From: "Joseph S. Myers" <joseph@codesourcery.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: DJ Delorie <dj@redhat.com>,
gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org,
newlib@sourceware.org
Subject: Re: On the toplevel configure and build system
Date: Tue, 29 Mar 2011 23:52:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1103292345210.2595@digraph.polyomino.org.uk> (raw)
In-Reply-To: <y0md3l9pka0.fsf@fche.csb>
On Tue, 29 Mar 2011, Frank Ch. Eigler wrote:
> Perhaps if we do move to git for all the /src stuff, we can have a
It is very strongly in my principle 6 that there should be no "we" moving
"for all the /src stuff" - that it should be made possible for each
project (a) through (i) to make its own decisions about version control
systems and repository hosting, and to have its own set of people with
write access, because the interdependencies associated with the shared
repository are one of the greatest flaws in the present system. I believe
it is already possible for cgen and rda to move our of src on their own
because they appear to have no dependence on the toplevel infrastructure.
(Other components would complicate merge issues if they move without the
toplevel repository (a) being created first.)
> /toplevel git repository with different branches suitable for each of
> your tastes of such policy.
I am hoping that the toplevel repository, (a) in my list, should not have
branches at all. All branching and tagging should take place in
repositories for individual projects (which could also choose when to
merge changes from the toplevel repository if merges at a particular time
are considered risky in the light of planned branches or releases).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2011-03-29 23:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 21:52 Joseph S. Myers
2011-03-29 22:28 ` DJ Delorie
2011-03-29 23:29 ` Joseph S. Myers
2011-03-29 23:41 ` Frank Ch. Eigler
2011-03-29 23:48 ` DJ Delorie
2011-03-29 23:52 ` Joseph S. Myers [this message]
2011-03-29 22:50 ` Geoffrey Keating
2011-03-30 0:07 ` Ian Lance Taylor
2011-03-29 23:45 ` Joseph S. Myers
2011-03-30 13:37 ` Tom Tromey
2011-03-30 15:16 ` Joseph S. Myers
2011-03-30 15:34 ` DJ Delorie
2011-03-30 15:54 ` Joseph S. Myers
2011-03-31 7:44 ` Paolo Bonzini
2011-03-31 12:09 ` Joseph S. Myers
2011-03-31 7:46 ` Paolo Bonzini
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.1103292345210.2595@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=dj@redhat.com \
--cc=fche@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=newlib@sourceware.org \
/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