From: DJ Delorie <dj@redhat.com>
To: nickc@redhat.com
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: Renaming mingw64 to mingw* for x86_64 architecure
Date: Mon, 08 Jan 2007 18:38:00 -0000 [thread overview]
Message-ID: <200701081837.l08IbvhK014114@greed.delorie.com> (raw)
In-Reply-To: <m3d55p2y5i.fsf@redhat.com> (message from Nick Clifton on Mon, 08 Jan 2007 18:04:09 +0000)
> Am I correct in assuming that your synchronisation scripts will
> bring this change into the sourceware repository, or should I apply
> the patch there as well ?
The toplevel scripts only advise the build maintainers that they're
out of sync. We have to manually sync those because they're
bidirectional and sometimes messy, and I haven't had the time or
desire to write the scripts needed to automate it.
The libiberty/ and include/ scripts do everything but the final commit
automatically (I have to push the "yes, please" button manually), and
always from gcc->src.
next prev parent reply other threads:[~2007-01-08 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 18:04 Nick Clifton
2007-01-08 18:38 ` DJ Delorie [this message]
2007-01-08 21:00 ` Andreas Tobler
2007-01-09 7:39 ` Nick Clifton
2007-01-09 13:45 ` Daniel Jacobowitz
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=200701081837.l08IbvhK014114@greed.delorie.com \
--to=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=nickc@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