From: Eli Zaretskii <eliz@gnu.org>
To: pmuldoon@redhat.com
Cc: gdb@sourceware.org
Subject: Re: GIT and CVS
Date: Thu, 13 Oct 2011 21:58:00 -0000 [thread overview]
Message-ID: <83r52g1rly.fsf@gnu.org> (raw)
In-Reply-To: <m3sjmwn0nh.fsf@redhat.com>
> From: Phil Muldoon <pmuldoon@redhat.com>
> Date: Thu, 13 Oct 2011 20:37:22 +0100
>
> GIT is, I think, available everywhere, has a CVS interface, and is
> far, far quicker than CVS.
Git is available on GNU/Linux, which is a lot, but it ain't
"everywhere".
My main development machines run MS-Windows. Git sucks on MS-Windows
(I don't like it much on GNU/Linux, either). If we are to switch to
git, it'll probably make me much less active as a member of the GDB
project.
If we are going to switch to a dVCS, git is not the only choice. I
like bzr better; bzr is a GNU project, unlike git.
next prev parent reply other threads:[~2011-10-13 21:58 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 19:37 Phil Muldoon
2011-10-13 20:21 ` Joseph S. Myers
2011-10-13 20:55 ` Phil Muldoon
2011-10-13 21:33 ` DJ Delorie
2011-10-13 21:44 ` Phil Muldoon
2011-10-13 21:43 ` Alfred M. Szmidt
2011-10-13 21:51 ` Jan Kratochvil
2011-10-13 22:08 ` Eli Zaretskii
2011-10-13 22:25 ` Jan Kratochvil
2011-10-13 22:41 ` Alfred M. Szmidt
2011-10-13 22:44 ` Alfred M. Szmidt
2011-10-14 10:31 ` Eli Zaretskii
2011-10-13 22:19 ` Alfred M. Szmidt
2011-10-13 22:45 ` Jan Kratochvil
2011-10-13 23:37 ` Alfred M. Szmidt
2011-10-14 5:56 ` Jan Kratochvil
2011-10-14 6:51 ` Alfred M. Szmidt
2011-10-13 23:03 ` Phil Muldoon
2011-10-13 23:51 ` Alfred M. Szmidt
2011-10-14 6:01 ` Jan Kratochvil
2011-10-14 6:52 ` Alfred M. Szmidt
2011-10-14 7:01 ` Jan Kratochvil
2011-10-14 7:13 ` Alfred M. Szmidt
2011-10-14 15:39 ` Joseph S. Myers
2011-10-14 15:49 ` Jan Kratochvil
2011-10-13 21:51 ` Joseph S. Myers
2011-10-13 21:59 ` Jan Kratochvil
2011-10-13 22:08 ` Joseph S. Myers
2011-10-13 22:17 ` Eli Zaretskii
2011-10-14 5:03 ` Joel Brobecker
2011-10-14 8:04 ` Eli Zaretskii
2011-10-13 23:14 ` Phil Muldoon
2011-10-13 23:56 ` Joseph S. Myers
2011-10-14 6:04 ` Jan Kratochvil
2011-10-13 21:58 ` Eli Zaretskii [this message]
2011-10-13 23:20 ` Phil Muldoon
2011-10-14 8:13 ` Eli Zaretskii
2011-10-14 10:23 ` Mark Kettenis
2011-10-14 10:55 ` Eli Zaretskii
2011-10-14 14:09 ` Li, Rongsheng
2011-10-14 12:54 ` Jan Kratochvil
2011-10-14 13:07 ` Jonas Maebe
2011-10-14 14:26 ` Eli Zaretskii
2011-10-14 14:32 ` Jan Kratochvil
2011-10-14 15:05 ` Phil Muldoon
2011-10-14 15:21 ` Eli Zaretskii
2011-10-14 14:52 ` Phil Muldoon
2011-10-14 15:05 ` Eli Zaretskii
2011-10-14 15:47 ` Jonas Maebe
2011-10-14 16:12 ` Andreas Schwab
2011-10-14 16:20 ` Andreas Schwab
2011-10-14 16:25 ` Eli Zaretskii
2011-10-14 17:06 ` Matt Rice
2011-10-14 17:25 ` Eli Zaretskii
2011-11-11 21:00 ` Steinar Bang
2011-11-12 8:30 ` Eli Zaretskii
2011-11-12 15:30 ` Steinar Bang
2011-10-14 5:10 ` Joel Brobecker
2011-10-14 15:38 ` Joseph S. Myers
2011-10-14 12:36 ` André Pönitz
2011-10-14 14:19 ` Eli Zaretskii
2011-10-14 15:02 ` Phil Muldoon
2011-10-14 15:16 ` Eli Zaretskii
2011-10-14 16:59 ` André Pönitz
2011-10-14 14:58 ` Phil Muldoon
2011-10-14 15:02 ` Paul_Koning
2011-10-16 15:04 ` Ralf Corsepius
2011-10-14 16:10 ` André Pönitz
2011-11-11 22:50 ` Pedro Larroy
2011-11-12 8:28 ` Steinar Bang
2011-11-13 0:05 ` John Hein
2011-11-15 15:02 ` Tom Tromey
2011-11-16 16:59 ` Christopher Faylor
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=83r52g1rly.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=pmuldoon@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).