public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Larroy <pedro.larroy.lists@gmail.com>
To: pmuldoon@redhat.com
Cc: gdb@sourceware.org
Subject: Re: GIT and CVS
Date: Fri, 11 Nov 2011 22:50:00 -0000	[thread overview]
Message-ID: <CAC_CU1gLJaqM5uPU0P1b5hj-wBxouveJHHfc_hhCxDORFZGYcw@mail.gmail.com> (raw)
In-Reply-To: <m3sjmwn0nh.fsf@redhat.com>

Why not mercurial? it's more user friendly than git, and better cross
platform support.


Regards.

On Thu, Oct 13, 2011 at 9:37 PM, Phil Muldoon <pmuldoon@redhat.com> wrote:
>
> At the risk of atomizing the poor horse, I want to refresh ideas and
> thoughts on this.
>
> First, I'll point out I am in favor of GIT.  Not because GIT has won me
> over heart-and-soul, but purely because I can work on GDB GIT offline.
> This is not an inconsiderable benefit.  I can create local check-ins,
> create branches, merge, cherry-pick all in the leisure of my own office,
> or garden, or airport ... without internet access.
>
> So that is my bias laid out.
>
> So why are we still on CVS?  I'm not a release manager, so I do not have
> to do the difficult work of cutting branches, and all of the difficult
> work in making releases.  But what are the objections to GIT?
> Personally, I'll give a strong bias to Joel's opinions because, frankly,
> he has to deal with this issue far more than any other.
>
> GIT is, I think, available everywhere, has a CVS interface, and is
> far, far quicker than CVS.  Maybe with the stronger identity and
> information that comes with GIT logs we can finally retire
> ChangeLogs.
>
> CVS has served very well over the years.  I, and many others, cut our
> teeth on it.  It's been a good system.  But beyond stability I
> don't see it keeping up with functionality of other repository systems.
> I find myself working on GIT 98% of the time, and the other 2% dealing
> with CVS on the final check-in.  Surely I can't be the only hacker that
> does this?  If the vast majority are in this work-flow, perhaps we
> should think about the pros and the cons again.  I have no ideas about
> the work-flows of my GDB hackers, and if, you know, we are all doing this
> then we should recognize the elephant in the room.  If not, then I will
> go happily into the (CVS) night, content on the validity of its use and
> utility.
>
> So, what do you think?
>
> Cheers,
>
> Phil
>

  parent reply	other threads:[~2011-11-11 22:50 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
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 [this message]
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=CAC_CU1gLJaqM5uPU0P1b5hj-wBxouveJHHfc_hhCxDORFZGYcw@mail.gmail.com \
    --to=pedro.larroy.lists@gmail.com \
    --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).