From: "Joseph S. Myers" <joseph@codesourcery.com>
To: gdb@sourceware.org
Subject: Re: What is keeping GDB in CVS ?
Date: Fri, 19 Jun 2009 19:29:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0906191927230.10731@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20090619192236.GA10670@ednor.casa.cgf.cx>
On Fri, 19 Jun 2009, Christopher Faylor wrote:
> So maybe they shouldn't be *shared*. There could be just one copy. I
> think everyone knows that you'll have problems as soon as you start
> duplicating data. This is no exception.
>
> I doubt that the gcc project would think it was a good idea but we could
> just break libiberty and the top-level configury into a separate
> repository too. Then when you make a change to a file, everyone gets
> the change and people will squawk immediately when you make a change to
> one of these files for gcc which happens to break a binutils build.
That worked for the old GNU hardlinks-to-,v-files approach. I don't think
it's effectively supported by any version control system more modern than
CVS.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2009-06-19 19:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 16:13 Samuel Bronson
2009-06-19 16:23 ` Daniel Jacobowitz
2009-06-19 16:28 ` Daniel Jacobowitz
2009-06-19 16:38 ` Christopher Faylor
2009-06-19 16:49 ` Daniel Jacobowitz
2009-06-19 16:56 ` Richard Earnshaw
2009-06-19 17:28 ` Daniel Jacobowitz
2009-06-19 17:30 ` Tom Tromey
2009-06-19 19:18 ` Joseph S. Myers
2009-06-19 17:18 ` Joseph S. Myers
2009-06-19 19:22 ` Christopher Faylor
2009-06-19 19:29 ` Joseph S. Myers [this message]
2009-06-20 18:48 ` Christopher Faylor
2009-06-20 19:19 ` Joseph S. Myers
2009-06-20 20:36 ` Christopher Faylor
2009-06-20 20:53 ` Jan Kratochvil
2009-06-25 21:45 ` Tom Tromey
2009-06-26 12:28 ` 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=Pine.LNX.4.64.0906191927230.10731@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gdb@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