From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: gdb@sourceware.org, Joel Brobecker <brobecker@adacore.com>,
binutils@sources.redhat.com,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: time to be serious about dropping CVS
Date: Sat, 02 Jan 2010 19:08:00 -0000 [thread overview]
Message-ID: <20100102190741.GA8480@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20100102181134.GB7365@ednor.casa.cgf.cx>
On Sat, Jan 02, 2010 at 01:11:34PM -0500, Christopher Faylor wrote:
>On Fri, Jan 01, 2010 at 06:18:06PM +0400, Joel Brobecker wrote:
>>Thanks for the suggestions!
>>
>>> Do not try to plan a transition for the whole src repository. Try to plan
>>> one for GDB and Binutils together at most [*], on the basis that other
>>> projects such as Cygwin and Newlib should choose their own version control
>>> systems in their own way and at such times as are convenient to them.
>>
>>I would be happy with such an approach - in fact, I think that makes
>>the task easier too, since we'd have fewer groups to coordinate.
>
>Although I'd like to move Cygwin to git, I really and sincerely think
>that making Cygwin part of the source tree for gdb and binutils is a
>historical mistake. I'd love to rectify it.
Hmm. On rereading the "Although" above doesn't really belong there
since I was just expressing my support for the idea. Sorry for the
lack of clarity.
cgf
next prev parent reply other threads:[~2010-01-02 19:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 8:02 Joel Brobecker
2010-01-01 8:35 ` Eli Zaretskii
2010-01-01 9:00 ` Joel Brobecker
2010-01-01 10:34 ` Eli Zaretskii
2010-01-01 15:39 ` Matthias Urlichs
2010-01-01 15:49 ` Eli Zaretskii
2010-01-01 10:26 ` Mark Kettenis
2010-01-01 10:46 ` Andreas Schwab
2010-01-01 11:03 ` Joel Brobecker
2010-01-01 16:06 ` Matthias Urlichs
2010-01-01 17:57 ` H.J. Lu
2010-01-01 13:00 ` Joseph S. Myers
2010-01-01 14:18 ` Joel Brobecker
2010-01-02 18:11 ` Christopher Faylor
2010-01-02 19:08 ` Christopher Faylor [this message]
2010-01-03 13:52 ` Matthias Urlichs
2010-01-08 12:58 ` Phil Muldoon
2010-01-08 13:08 ` Tristan Gingold
2010-01-08 13:20 ` Joel Brobecker
2010-01-08 13:26 ` Tristan Gingold
2010-01-08 13:13 ` Joel Brobecker
2010-01-08 13:21 ` Jonas Maebe
2010-01-08 13:34 ` Andreas Schwab
2010-01-08 13:14 ` Jonas Maebe
2010-01-08 18:41 ` Michael Snyder
2010-01-08 18:49 ` Paul Koning
2010-12-20 17:35 ` Joseph S. Myers
2010-12-21 3:27 ` Joel Brobecker
2010-12-21 3:46 ` Jim Blandy
2010-12-21 7:16 ` Pascal Obry
2010-12-21 15:14 ` Tom Tromey
2010-12-21 16:15 ` Christopher Faylor
2010-12-21 18:39 ` Joseph S. Myers
2010-12-21 19:26 ` Tom Tromey
2010-12-21 18:42 ` Joseph S. Myers
2010-12-21 19:21 ` DJ Delorie
2010-12-22 15:23 ` Christopher Faylor
2010-12-22 15:29 ` NightStrike
2010-12-22 16:48 ` Joseph S. Myers
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=20100102190741.GA8480@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=binutils@sources.redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=joseph@codesourcery.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