All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Segato <daniele.bilug@gmail.com>
To: newsgroups@catchall.shelter13.net
Cc: git@vger.kernel.org
Subject: Re: Deciding between Git/Mercurial
Date: Tue, 29 Sep 2009 10:44:19 +0200	[thread overview]
Message-ID: <9accb4400909290144t1363b5c6t8886bfa01e486c94@mail.gmail.com> (raw)
In-Reply-To: <h9nlhj$heq$1@ger.gmane.org>

On Sun, Sep 27, 2009 at 2:24 PM, Anteru
<newsgroups@catchall.shelter13.net> wrote:
> I'm currently evaluating DVCS for a project, and we're at a point where
> it comes down to either Mercurial or Git. Right now, I'm advocating for
> Git, while my co-workers like Mercurial, so I'd like to provide some
> good arguments in favor of git. Unfortunately, I'm not a git expert, so
> I hope I can get some help here ...
>
> First of all, what's the matter with git and Windows, is there some
> long-term commitment to make git work on Windows as well as on Linux?
> I'm using msysgit on Windows, and personally I'm happy with it, but my
> co-workers constantly nag that Mercurial has superior portability ...


Can I propose to make this discussion cross-mailing list adding the hg
mailing list to the CC?
I think it would be a good discussion if we don't end up flaming.
Let me know what you think about it


about the Windows+Git compatibility, you may consider TortoiseGit too
for the not-CLI-oriented guys; I've seen it a while ago and it seems
pettry well integrated with windows


> Mercurial's revision number system: With git, I get an SHA1 hash for
> every commit, but it's not possible to see whether Hash1 is newer than
> Hash2, while Mecurial also adds a running number to each commit. What's
> the rationale behind this decision for git, and is it possible to
> emulate Mercurial's behavior somehow?


If you tag a commit then you should be able to see how many commits
there are from that one issuing a git describe
(found on the internet)
git commit -m'Commit One.'
git tag -a -m'Tag One.' 1.2.3
git describe    # => 1.2.3
git commit -m'Commit Two.'
git describe    # => 1.2.3-1-gaac161d
git commit -m'Commit Three.'
git describe    # => 1.2.3-2-g462715d
git tag -a -m'Tag Two.' 2.0.0
git describe    # => 2.0.0


> So far, my key arguments are that git is more robust (more projects
> using it, larger developer base), of course git's excellent performance
> and the much better support for SVN, which is important for us as we can
> slowly migrate from SVN->Git, while hgmercurial is still in the making
> (and Python's SVN->Hg switch is for instance waiting for it).

  parent reply	other threads:[~2009-09-29  8:44 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-27 12:24 Deciding between Git/Mercurial Anteru
2009-09-27 18:01 ` Robin Rosenberg
2009-09-27 18:10   ` Anteru
2009-09-27 18:44     ` Alex Riesen
2009-09-27 18:51       ` Mark Struberg
2009-09-27 19:18         ` Anteru
2009-09-27 19:31           ` Alex Riesen
2009-09-27 19:34           ` Erik Faye-Lund
2009-09-27 18:55     ` Pascal Obry
2009-10-22  8:01   ` Martin Langhoff
2009-09-28  8:36 ` Felipe Contreras
2009-09-28  8:42   ` Matthieu Moy
2009-09-28 10:08   ` Johannes Schindelin
2009-09-28 11:01     ` Felipe Contreras
2009-09-28 11:17       ` Bruce Stephens
2009-09-30 11:14     ` Matthias Andree
2009-09-28 11:32 ` Dilip M
2009-09-28 20:54 ` Damien Wyart
2009-09-28 21:09   ` Steven Noonan
2009-09-28 21:33     ` Sverre Rabbelier
2009-09-28 23:56       ` Randal L. Schwartz
2009-09-29  0:01         ` Sverre Rabbelier
2009-09-29  7:44         ` Mike Ralphson
2009-09-29  8:21       ` Matthieu Moy
2009-09-29  8:22         ` Sverre Rabbelier
2009-09-28 23:11 ` Jakub Narebski
2009-09-29  0:32   ` Jakub Narebski
2009-09-29  6:32   ` Anteru
2009-09-29 18:44   ` Leo Razoumov
2009-09-29 18:58     ` Jakub Narebski
2009-09-29 19:55       ` Matthieu Moy
2009-09-30  0:49       ` Leo Razoumov
2009-09-30  6:28         ` Björn Steinbrink
2009-09-30  9:17         ` Andreas Ericsson
2009-09-30 11:09         ` Jakub Narebski
2009-09-29  1:55 ` Paolo Bonzini
2009-09-29  8:44 ` Daniele Segato [this message]
2009-09-29  8:54   ` Dilip M
2009-09-30 11:09 ` Matthias Andree
2009-09-30 22:05   ` Daniel Barkalow
2009-10-22  2:38 ` Dilip M
2009-10-22  6:50   ` Anteru
2009-10-22  7:12     ` Dilip M
2009-10-22  7:35       ` Anteru

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=9accb4400909290144t1363b5c6t8886bfa01e486c94@mail.gmail.com \
    --to=daniele.bilug@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=newsgroups@catchall.shelter13.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.