From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: Tom Tromey <tromey@redhat.com>,
GDB Development <gdb@sourceware.org>,
Binutils Development <binutils@sourceware.org>
Subject: Re: A Proposal to Move to Git
Date: Sat, 31 Aug 2013 16:58:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1308311651190.20398@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.BSF.2.02.1308302130560.41348@arjuna.pair.com>
On Fri, 30 Aug 2013, Hans-Peter Nilsson wrote:
> > Rather, changing shared files now needs three repositories rather than two
> > to change. If we can get agreement on GCC as the master, this could be
> > automated as it is for libiberty (check into GCC and let the automatic
> > process merge to the others).
>
> Or two repos rather than one and agreement whether src-CVS or
> the new git is the master; some files are not in GCC.
Well, such agreement for those files not in GCC (we already have GCC as
master for libiberty and libdecnumber, for example) - unless and until we
move the non-shared parts of include/ to a separate directory, which I
think would be better. (See
<https://sourceware.org/ml/binutils/2013-08/msg00207.html> for my comments
on the division of include/, with an unresolved question about whether
anything not shared with GCC is used by anything outside of binutils+gdb.)
> For other projects not to be severely inconvenienced (i.e. to
> actually leave them free to choose) we assume here that the src
> CVS repo remains updated regarding shared files. I did not take
> that for granted; it seemed that shared directories would remain
> read-only, but I guess that wasn't actually intended.
I consider it necessary that shared files get updated in all the
repositories between which they are shared (with the possibility of
removing files when no longer needed by anything in a particular
repository).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2013-08-31 16:58 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 21:12 Tom Tromey
2013-08-20 21:16 ` Andrew Pinski
2013-08-20 21:26 ` Joseph S. Myers
2013-08-20 21:19 ` Joel Brobecker
2013-08-20 21:21 ` Paul_Koning
2013-08-20 22:59 ` Phil Muldoon
2013-08-21 15:05 ` Eli Zaretskii
2013-08-21 15:32 ` Andreas Schwab
2013-08-21 15:54 ` Eli Zaretskii
2013-08-26 8:05 ` Andreas Schwab
2013-08-21 18:40 ` Steinar Bang
2013-08-21 20:05 ` Eli Zaretskii
2013-08-21 20:38 ` Andreas Schwab
2013-08-22 18:56 ` Florian Weimer
2013-08-21 15:38 ` Steve Ellcey
2013-08-21 15:50 ` Joel Brobecker
2013-08-22 6:10 ` Tristan Gingold
2013-08-22 14:16 ` Richard Earnshaw
2013-08-22 14:25 ` Joel Brobecker
2013-08-22 14:39 ` Fred Cooke
2013-08-22 20:10 ` Mark Kettenis
2013-08-22 20:21 ` Fred Cooke
2013-08-22 20:22 ` David Miller
2013-08-22 20:48 ` Andrew Pinski
2013-08-22 21:07 ` Andreas Schwab
2013-08-22 21:10 ` Tom Tromey
2013-08-23 15:40 ` H.J. Lu
2013-08-23 15:55 ` Joel Brobecker
2013-08-23 16:03 ` Paul_Koning
2013-08-23 16:05 ` H.J. Lu
2013-08-26 12:37 ` NightStrike
[not found] ` <upzc38pvcv1w.fsf@dod.no>
2013-08-27 16:21 ` asmwarrior
2013-08-23 16:03 ` H.J. Lu
2013-08-23 16:09 ` Joel Brobecker
2013-08-23 16:24 ` Matt Rice
2013-08-23 16:37 ` H.J. Lu
2013-08-23 16:47 ` Matt Rice
2013-08-23 17:01 ` H.J. Lu
[not found] ` <87siy070su.fsf@dod.no>
2013-08-24 0:27 ` Doug Evans
2013-08-22 23:55 ` Alan Modra
2013-08-30 22:58 ` Hans-Peter Nilsson
2013-08-30 23:37 ` Joseph S. Myers
2013-08-31 2:05 ` Hans-Peter Nilsson
2013-08-31 16:58 ` Joseph S. Myers [this message]
2013-09-04 16:55 ` Doug Evans
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.1308311651190.20398@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=gdb@sourceware.org \
--cc=hp@bitrange.com \
--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