From: Christopher Faylor <me@cgf.cx>
To: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: section _raw_size and _cooked_size
Date: Tue, 15 Jun 2004 02:00:00 -0000 [thread overview]
Message-ID: <20040615020155.GA30252@trixie.casa.cgf.cx> (raw)
In-Reply-To: <20040615014018.GE6207@bubble.modra.org>
On Tue, Jun 15, 2004 at 11:10:18AM +0930, Alan Modra wrote:
>On Mon, Jun 14, 2004 at 07:04:06PM -0400, Andrew Cagney wrote:
>> ok for gdb/sim (the changes are mindlessly mechanical).
>
>They're in. Apologies to anyone who checked out the tree between
>2004/06/15 01:04Z and 2004/06/15 01:25Z, as it no doubt was broken
>due to being only partially committed.
>
>The winsup/utils/ changes aren't in yet. Who gives the OK there?
>cgf? http://sources.redhat.com/ml/binutils/2004-06/msg00210.html
Yep. Go ahead. You have carte blanche to make bfd related changes
in winsup/utils, as far as I'm concerned.
I appreciate that you took this into consideration very much, btw.
cgf
prev parent reply other threads:[~2004-06-15 2:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 1:24 Alan Modra
2004-06-14 23:04 ` Andrew Cagney
2004-06-15 1:40 ` Alan Modra
2004-06-15 2:00 ` Christopher Faylor [this message]
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=20040615020155.GA30252@trixie.casa.cgf.cx \
--to=me@cgf.cx \
--cc=binutils@sources.redhat.com \
--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