From: Santi Béjar <sbejar@gmail.com>
Date: Wed, 28 May 2008 14:50:54 GMT
Subject: Re: git-svn commit id.
Message-ID: <8aa486160805280750q5a214961re21ed1dc731cf181@mail.gmail.com>
In-Reply-To: <483D6F10.5000403@op5.se>

On Wed, May 28, 2008 at 4:41 PM, Andreas Ericsson <ae@op5.se> wrote:
> Victor Bogado da Silva Lins wrote:
>>
>> I have two git-svn repositories here and I noticed that the same commit
>> have different ids in them. How this came to be, both commits share the
>> exact same git-svn-id and are the same (as far as I know).
>
> If the have exactly the same history leading up to them, source trees
> and commit object (including timestamps), the only way they can be any
> different is if you've run into a bug in the SHA1 libraries.
>
> If either of the above three are different though, you *will* end up
> with different commits.
>
> Try doing "git cat-file commit <sha1-of-one-commit>" and then
> "git cat-file commit <sha1-of-other-commit>". If you take a diff
> between the two, you'll see how they differ (my guess would be the
> timestamps)
>

Git-svn uses the same timestamps as in svn, my guess is that one has
more history than the other.

Santi