From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: jim@meyering.net, hjl.tools@gmail.com, tromey@redhat.com,
gdb@sourceware.org
Subject: Re: gdb.git mirror is broken
Date: Tue, 06 Oct 2009 18:38:00 -0000 [thread overview]
Message-ID: <83vdismktw.fsf@gnu.org> (raw)
In-Reply-To: <20091006154536.GR29600@adacore.com>
> Date: Tue, 6 Oct 2009 08:45:37 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: "H.J. Lu" <hjl.tools@gmail.com>, Tom Tromey <tromey@redhat.com>, GDB <gdb@sourceware.org>
>
> > If anyone is interested in switching primary GDB development
> > to git, once such a new repository is in place and deemed stable,
> > I urge you to dump CVS. While the conversion tools are not always
> > reliable, I can assure you that git itself has been amazingly reliable
> > for years.
>
> I think we're not quite ready to switch to any other version management
> system right now, unfortunately. But I strongly support a switch to git.
git is a PITA on Windows, which is a major issue for me.
next prev parent reply other threads:[~2009-10-06 18:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 0:31 H.J. Lu
2009-10-06 6:23 ` Pierre Muller
2009-10-06 6:45 ` Jim Meyering
2009-10-06 6:51 ` Jim Meyering
2009-10-06 7:38 ` Jim Meyering
2009-10-06 13:08 ` H.J. Lu
2009-10-06 14:07 ` Jim Meyering
2009-10-06 14:26 ` Joseph S. Myers
2009-10-06 14:33 ` Jim Meyering
2009-10-06 16:11 ` Joseph S. Myers
2009-10-07 4:29 ` Matt Rice
2009-10-10 5:35 ` Matt Rice
2009-10-06 16:06 ` Tom Tromey
2009-10-06 16:21 ` Jim Meyering
2009-10-06 15:45 ` Joel Brobecker
2009-10-06 18:38 ` Eli Zaretskii [this message]
2009-10-06 19:01 ` Joel Brobecker
2009-10-06 20:36 ` Eli Zaretskii
2009-10-06 21:10 ` Joel Brobecker
2009-10-06 22:04 ` Tom Tromey
2009-10-07 7:29 ` Eli Zaretskii
2009-10-07 7:27 ` Eli Zaretskii
2009-10-06 16:08 ` Tom Tromey
2009-10-06 16:09 ` Jim Meyering
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=83vdismktw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=jim@meyering.net \
--cc=tromey@redhat.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