All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: SLONIK.AZ@gmail.com
Cc: Jakub Narebski <jnareb@gmail.com>,
	Anteru <newsgroups@catchall.shelter13.net>,
	git@vger.kernel.org
Subject: Re: Deciding between Git/Mercurial
Date: Wed, 30 Sep 2009 11:17:30 +0200	[thread overview]
Message-ID: <4AC3222A.2040305@op5.se> (raw)
In-Reply-To: <ee2a733e0909291749s71801b29ufa827cab715d0abb@mail.gmail.com>

On 09/30/2009 02:49 AM, Leo Razoumov wrote:
> On 2009-09-29, Jakub Narebski<jnareb@gmail.com>  wrote:
>> On Tue, 29 Sep 2009, Leo Razoumov wrote:
>>   >  On 2009-09-28, Jakub Narebski<jnareb@gmail.com>  wrote:
>>   >  >  [..snip..]
>>   >  >   Besides with nonlinear history with
>>   >  >   revision numbers such as 12678 and 12687 you know that 12678 is older
>>   >  >   than 12687 if and only if 12678 and 12687 are on the same line of
>>   >  >   development.
>>   >
>>   >  The statement above is incorrect!! In a Mercurial repo local revision
>>   >  numbers are strictly ordered in commit time. 12678<  12687 means that
>>   >  12678 was committed prior to 12687. But these two commits could belong
>>   >  to two completely unrelated lines of development.
>>
>>
>> This is impossible with distributed development.  If the second branch
>>   comes from other repository, with commits _created_ (in that repository)
>>   earlier than commits in current repository, but commits in first
>>   branch (from current repository) were created earlier than _fetching_
>>   those commits in second branch:
>>
>>    .---.---.---.---x---1---2---3---M---.
>>                     \             /
>>                      \-A---B---C-/<-- from repository B
>>
>>
>>   Either you would have to change commits numbers, and therefore they would
>>   be not stable, or you would have to change commit time to mean 'time this
>>   commit got into current repository', which would kill performance for sure.
>>
>
> Jakub,
> in Mercurial sequential commit numbers are local to a repo and are not
> unique between the clones. Unique ID is SHA1 as in git. So mercurial
> commit 127:aaf123453dfgdfgddd...
> means commit number 127 in this repo with SHA1 "aaf123453dfgdfgddd..."
> In another clone commit 127 might mean completely different thing.
> Sequential commit numbers are strictly for "local convenience".
>

Personally I much prefer the "commit'ish-backward" notation of git,
where HEAD~4 means "the commit 4 commits back from HEAD".

You'd get awfully tired of writing the six-digit "shorthand" numbers
of large projects fairly quickly, I imagine.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

  parent reply	other threads:[~2009-09-30  9:18 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 [this message]
2009-09-30 11:09         ` Jakub Narebski
2009-09-29  1:55 ` Paolo Bonzini
2009-09-29  8:44 ` Daniele Segato
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=4AC3222A.2040305@op5.se \
    --to=ae@op5.se \
    --cc=SLONIK.AZ@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --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.