From: Ian Lance Taylor <ian@airs.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb@sourceware.org
Subject: Re: Moving GDB sources to subversion?
Date: Fri, 28 Oct 2005 23:08:00 -0000 [thread overview]
Message-ID: <m3fyqlz1cd.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20051028230207.GZ1155@adacore.com>
Joel Brobecker <brobecker@adacore.com> writes:
> > > I think GCC is getting ready to move to subversion as the revision
> > > control system. Is there any similar plan for GDB?
> >
> > Why should we?
>
> I wasn't implying that we should. I haven't seen any discussion about
> this (but maybe I missed them). However, I have heard rumors that GCC
> *is* going to move to svn. I think GCC and GDB have been in the same
> physical repository so far (src?), so I was afraid that a change for
> GCC would necessarily impact GDB.
gcc has moved to subversion. The conversion finished today.
This does not affect gdb. At present gdb, binutils, newlib, and
cygwin share a single CVS repository. gcc is in a subversion
repository.
This does affect anybody using the uberbaum pseudo-repository; if you
don't know what that is, don't ask.
It would be simpler for the sourceware.org overseers (including
myself) if every project converted to subversion. And subversion does
have some advantages over CVS.
But really each project is going to have to decide for itself whether
to switch or not.
(If you want to switch to something other than CVS or subversion, you
will have to be prepared to convince the overseers to do whatever
management is required by whatever new system is chosen. Daniel
Berlin went through that process for subversion for gcc.)
Hope this helps.
Ian
next prev parent reply other threads:[~2005-10-28 23:08 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 [this message]
2005-10-29 0:15 ` H. J. Lu
2005-10-28 23:14 ` Daniel Jacobowitz
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
2005-10-28 23:25 ` Joel Brobecker
2005-10-28 23:57 ` Christopher Faylor
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=m3fyqlz1cd.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--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