From: Eli Zaretskii <eliz@gnu.org>
To: cagney@gnu.org
Cc: mark.kettenis@xs4all.nl, drow@false.org, gdb@sourceware.org
Subject: Re: A case for `void *' for pointers to arbitrary (byte) buffers
Date: Wed, 04 May 2005 17:57:00 -0000 [thread overview]
Message-ID: <E1DTO6n-00007B-7s@fencepost.gnu.org> (raw)
In-Reply-To: <4278EC18.1000308@gnu.org> (message from Andrew Cagney on Wed, 04 May 2005 11:36:56 -0400)
> Date: Wed, 04 May 2005 11:36:56 -0400
> From: Andrew Cagney <cagney@gnu.org>
>
> To ensure that our byte buffers are compatible with BFDs we'll want to use
> "typedef bfd_byte gdb_byte" anyway.
Can you explain why? I don't see why we will want that.
> Anyway, since the prefered name is "gdb_byte", and that was Eli's idea,
> I think it is fit and proper that Eli take the honours. Can we get it
> done by tomorrow?
If ``we'' here means me, then no, ``we'' cannot do this by tomorrow.
I won't have enough free time until then, and on top of that, since
the FSF moved to their new offices, I have trouble even reading my
mail, let alone doing something more serious. Sorry.
next prev parent reply other threads:[~2005-05-04 17:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42710E90.3030300@gnu.org>
[not found] ` <200504281919.j3SJJKF1011501@elgar.sibelius.xs4all.nl>
[not found] ` <42715EE8.5070704@gnu.org>
[not found] ` <01c54c8a$Blat.v2.4$ffbe8140@zahav.net.il>
[not found] ` <42753958.70109@gnu.org>
[not found] ` <01c54e92$Blat.v2.4$5cf24460@zahav.net.il>
[not found] ` <42755FD4.8000009@gnu.org>
[not found] ` <01c54f4a$Blat.v2.4$a9fc8500@zahav.net.il>
[not found] ` <42778DE6.1080106@gnu.org>
2005-05-03 20:17 ` Mark Kettenis
2005-05-03 20:23 ` Daniel Jacobowitz
2005-05-03 21:14 ` Mark Kettenis
2005-05-03 21:16 ` Daniel Jacobowitz
2005-05-03 22:10 ` Mark Kettenis
2005-05-03 22:28 ` Daniel Jacobowitz
2005-05-03 22:31 ` Joel Brobecker
2005-05-04 14:45 ` Mark Kettenis
2005-05-04 20:36 ` Eli Zaretskii
2005-05-04 15:40 ` Andrew Cagney
2005-05-04 17:57 ` Eli Zaretskii [this message]
2005-05-03 22:01 ` Stan Shebs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1DTO6n-00007B-7s@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox