From: Phil Muldoon <pmuldoon@redhat.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: meeting notes 20070905
Date: Wed, 05 Sep 2007 14:41:00 -0000 [thread overview]
Message-ID: <46DEBFF9.9060807@redhat.com> (raw)
In-Reply-To: <46DEBB8C.6090608@oracle.com>
Elena Zannoni wrote:
Some further notes. Minutes as an attachment make in-line comments
painful :(
> Frysk meeting 2007-09-05
>
> Version control systems discussions
>
> Tim Andrew Elena Stan Mark Sami [who else?]
>
Phil
> Do people that prefer strongly one system have played around with the
> others as well?
>
> Tim --> likes Git, hasn't tried Hg
> Mark --> Hg
Phil --> either, as long as it is not CVS. We have decades of combined
CVS experience, yet there are still mistakes made daily. Some of which
take hours and hours to recover from. At some point have to look at the
tool, and not the developer and perhaps think that a newer, better one
is needed. Personally (further down) there are lots of projects moving
to DCM. Including OpenJDK, Mozilla, Kernel, ASLA, Xen, RPM, etc etc to
name a few. I find the "stay with CVS as it is known" a bit of a false
argument. Borked and old != better.
> Plugins: cvs plugin in eclipse. No other plugins for eclipse.
> cvs module in emacs as well. no emacs modes for git and Hg.
Incorrect at least for Mercurial:
http://www.selenic.com/mercurial/wiki/index.cgi/OtherTools
No idea about GiT though I am sure Tim will fill in.
> Advantage over cvs is that one can recover easily from erroneous
> commits, because of the changesets.
Active developer community, saner interface (goodbye to positional
switches!). Trac and Maven integration.
> What projects we know of are using Git and which ones are using Hg?
>
> Git: kernel, libunwind
> Hg: icedtea, openjdk, mozilla
For Mercurial
http://www.selenic.com/mercurial/wiki/index.cgi/ProjectsUsingMercurial
I'll fill all this data into the webpage, too.
Regards
Phil
next prev parent reply other threads:[~2007-09-05 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 14:22 Elena Zannoni
2007-09-05 14:41 ` Phil Muldoon [this message]
2007-09-07 7:38 ` Tim Moore
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=46DEBFF9.9060807@redhat.com \
--to=pmuldoon@redhat.com \
--cc=frysk@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).