From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Tom Tromey <tromey@redhat.com>,
GDB Development <gdb@sourceware.org>,
Binutils Development <binutils@sourceware.org>
Subject: Re: merging from gcc
Date: Mon, 11 Nov 2013 16:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1311111652250.18663@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20131110193858.GH18885@lug-owl.de>
On Sun, 10 Nov 2013, Jan-Benedict Glaw wrote:
> On Fri, 2013-11-08 11:11:09 -0700, Tom Tromey <tromey@redhat.com> wrote:
> > I've finally set up some semi-automatic merging from gcc to
> > binutils-gdb.git.
>
> What about merging other external stuff? For the binutils/gdb repo, I
> have this in mind:
Any such merges of shared files maintained elsewhere, please update all of
GCC SVN, binutils-gdb git and src CVS at the same time, rather than just a
subset. (As the files you mention should always come verbatim from
upstream, you don't need to worry about cases where people have changed
the different repositories in different ways and you have to do a
multi-way merge - you should just be able to copy in the latest version to
all three repositories.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2013-11-11 16:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 18:20 Tom Tromey
2013-11-08 18:44 ` Doug Evans
2013-11-08 18:47 ` Tom Tromey
2013-11-08 19:10 ` Doug Evans
2013-11-08 19:53 ` DJ Delorie
2013-11-11 19:45 ` Doug Evans
2014-10-31 19:26 ` Doug Evans
2013-11-08 19:10 ` DJ Delorie
2013-11-11 19:35 ` Doug Evans
2013-11-08 22:28 ` Pedro Alves
2013-11-11 15:31 ` Tom Tromey
2013-11-08 22:33 ` Jan-Benedict Glaw
2013-11-10 19:39 ` Jan-Benedict Glaw
2013-11-11 14:57 ` Tom Tromey
2013-11-11 16:54 ` Joseph S. Myers [this message]
2013-11-11 19:19 ` Jan-Benedict Glaw
2013-11-11 22:12 ` Joseph S. Myers
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=Pine.LNX.4.64.1311111652250.18663@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=jbglaw@lug-owl.de \
--cc=tromey@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