public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <me@cgf.cx>
To: gdb@sourceware.org
Subject: Re: Moving GDB sources to subversion?
Date: Fri, 28 Oct 2005 23:57:00 -0000	[thread overview]
Message-ID: <20051028235750.GB17968@trixie.casa.cgf.cx> (raw)
In-Reply-To: <20051028232553.GB1155@adacore.com>

On Fri, Oct 28, 2005 at 04:25:53PM -0700, Joel Brobecker wrote:
>>I'd rather not rehash the months of discussion from the GCC list about
>>this :-)
>>
>>From my point of view:
>
>It is not my intention to push in any direction.  I'll be happy to move
>to svn if most of us think it's better, but I'm also happy to stick to
>CVS.

As Ian said, from the point of view of the people who maintain sourceware,
it would be easier if everything (or at least every substantial project)
moved to using subversion.  The benefits have been outlined already.

FWIW, we'll probably move cygwin to subversion as soon as the gcc dust
has settled.

cgf

  reply	other threads:[~2005-10-28 23:57 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 [this message]
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-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=20051028235750.GB17968@trixie.casa.cgf.cx \
    --to=me@cgf.cx \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).