From: Mark Kettenis <kettenis@gnu.org>
To: cagney@gnu.org
Cc: eliz@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [commit] Tighten memory read/write methods
Date: Fri, 28 Jan 2005 20:21:00 -0000 [thread overview]
Message-ID: <200501282021.j0SKL8ho001959@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <41FA88EE.2030109@gnu.org> (message from Andrew Cagney on Fri, 28 Jan 2005 13:48:14 -0500)
Date: Fri, 28 Jan 2005 13:48:14 -0500
From: Andrew Cagney <cagney@gnu.org>
Eli,
Like I said to Mark:
> We can certainly debate the merits of ISO vs BFD and bfd_byte vs
> void [vs gdb_byte], however lets keep that debate separate to my
> current task - getting constants sufficiently propogated for me
> to do my next value.h commit which in turn finishes DW_OP_piece.
You can constify without introducing bfd_byte.
Mark
next prev parent reply other threads:[~2005-01-28 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 20:11 Andrew Cagney
2005-01-27 21:04 ` Mark Kettenis
2005-01-27 23:06 ` Andrew Cagney
2005-01-28 8:46 ` Mark Kettenis
2005-01-28 11:43 ` Eli Zaretskii
2005-01-28 18:48 ` Andrew Cagney
2005-01-28 20:21 ` Mark Kettenis [this message]
2005-01-29 10:33 ` Eli Zaretskii
2005-01-27 21:05 ` Mark Kettenis
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=200501282021.j0SKL8ho001959@elgar.sibelius.xs4all.nl \
--to=kettenis@gnu.org \
--cc=cagney@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/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