From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: brobecker@adacore.com, gdb@sources.redhat.com
Subject: Re: Moving GDB sources to subversion?
Date: Mon, 07 Nov 2005 00:27:00 -0000 [thread overview]
Message-ID: <20051107002708.GB20613@nevyn.them.org> (raw)
In-Reply-To: <200510282324.j9SNOHql024377@elgar.sibelius.xs4all.nl>
On Sat, Oct 29, 2005 at 01:24:17AM +0200, Mark Kettenis wrote:
> > Date: Fri, 28 Oct 2005 19:14:30 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > On Sat, Oct 29, 2005 at 12:56:02AM +0200, Mark Kettenis wrote:
> > >
> > > Why should we?
> >
> > I'd rather not rehash the months of discussion from the GCC list about
> > this :-)
>
> The we're on the same wavelength. Let's put our effort into improving
> GDB; not in changing our infrastructure, let alone discussions about
> our infrastructure.
On the contrary, I think I could do GDB development more effectively if
it were not managed by CVS. Subversion is a lot more useful for things
like branching, and finding bug fixes to merge them back to an old
release branch your customers are still using. Which I waste a lot of
time on.
The only reason I'm not being more vocal about my preference to switch
is that the src repository poses certain unique challenges that GCC
didn't. Specifically, while cvs modules are insufficient for our
needs, we've gotten used to their quirks and can cope with them.
Subversion would have a whole different set of problems if you didn't
want to check out the whole src tree.
I don't think it's feasible for us to switch until someone has invested
some time thinking about that problem, and coming up with a better
solution than anything I've come up with so far.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-07 0:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 22:23 Joel Brobecker
2005-10-28 22:53 ` Simon Richter
2005-10-28 22:56 ` Mark Kettenis
2005-10-28 23:02 ` Joel Brobecker
2005-10-28 23:04 ` Andreas Tobler
2005-10-28 23:08 ` Ian Lance Taylor
2005-10-29 0:15 ` H. J. Lu
2005-10-28 23:14 ` Daniel Jacobowitz
2005-10-28 23:25 ` Joel Brobecker
2005-10-28 23:57 ` Christopher Faylor
2005-10-28 23:25 ` Mark Kettenis
2005-10-28 23:56 ` Nick Roberts
2005-10-29 10:57 ` Eli Zaretskii
2005-10-30 0:11 ` Ian Lance Taylor
2005-10-30 4:27 ` Eli Zaretskii
2005-10-30 2:47 ` Bob Rossi
2005-10-30 4:38 ` Ian Lance Taylor
2005-10-30 4:56 ` Daniel Jacobowitz
2005-11-07 0:27 ` Daniel Jacobowitz [this message]
2005-10-29 2:49 ` Stan Shebs
2005-11-02 22:56 ` Jim Blandy
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=20051107002708.GB20613@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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