public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org
Subject: Re: RFC: Moving gcc/intl to toplevel; syncing both copies to 0.12.1
Date: Thu, 03 Jul 2003 16:01:00 -0000	[thread overview]
Message-ID: <3F045338.90803@redhat.com> (raw)
In-Reply-To: <873choyfse.fsf@codesourcery.com>

> Andrew Cagney <ac131313@redhat.com> writes:
> 
> 
>>> I'd like to do this today, and commit to both gcc and src CVS
>>> as soon as I've tested it; it is blocking another major change
>>> over in gcc land, which needs to happen this week.  Will this be
>>> okay?  Does anyone know a reason why upgrading to 0.12.1 is a bad idea?
> 
>>
>> Can you two stage this - import into GCC, and then a week or so later,
>> import in to SRC?  That way the group with the most to gain (and
>> apparently the greatest urgency) experience the most pain :-)
> 
> 
> I could do that;

Thanks!  How does this stand with binutils?

Andrew



      parent reply	other threads:[~2003-07-03 16:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 17:07 Zack Weinberg
2003-07-02 17:49 ` Andrew Cagney
2003-07-02 17:56   ` Zack Weinberg
2003-07-02 17:59     ` Phil Edwards
2003-07-03 16:01     ` Andrew Cagney [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=3F045338.90803@redhat.com \
    --to=ac131313@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=zack@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).