From: Daniel Jacobowitz <drow@false.org>
To: Samuel Bronson <naesten@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: What is keeping GDB in CVS ?
Date: Fri, 19 Jun 2009 16:23:00 -0000 [thread overview]
Message-ID: <20090619162308.GA13968@caradoc.them.org> (raw)
In-Reply-To: <87r5xgqk0k.wl%naesten@gmail.com>
On Fri, Jun 19, 2009 at 12:13:31PM -0400, Samuel Bronson wrote:
> Hi. I'm wondering what the reasons are that GDB is still using CVS.
> In other words: what work must be done in order for it to be possible
> to switch it over to Git or Bzr?
Two things. One is a compelling reason to switch. (This is not an
invitation; there's plenty of discussion of this in the archives.
Personally I'd be happy to switch, but I'm easy to convince plus
having it in CVS is a real nuisance for me.)
The other thing is the combined src repository, which is shared
between many projects including binutils, newlib, cgen, and gdb. I
think we need to either decide to split them up and manage the shared
directories specially, or come up with a clever way to fake
CVS-style modules. Or else give up and make people check out the
whole thing, which might drive projects out into a new repository
anyway; a src checkout is bigger than anyone needs.
There was another discussion of this on the binutils list recently.
http://sourceware.org/ml/binutils/2009-05/msg00028.html
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-06-19 16:23 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 [this message]
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
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=20090619162308.GA13968@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=naesten@gmail.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