git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Santi Béjar" <sbejar@gmail.com>
To: "Andreas Ericsson" <ae@op5.se>
Cc: "Victor Bogado da Silva Lins" <victor@bogado.net>, git@vger.kernel.org
Subject: Re: git-svn commit id.
Date: Wed, 28 May 2008 16:50:54 +0200	[thread overview]
Message-ID: <8aa486160805280750q5a214961re21ed1dc731cf181@mail.gmail.com> (raw)
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

  reply	other threads:[~2008-05-28 14:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 14:02 git-svn commit id Victor Bogado da Silva Lins
2008-05-28 14:41 ` Andreas Ericsson
2008-05-28 14:50   ` Santi Béjar [this message]
2008-05-28 16:18     ` Victor Bogado da Silva Lins

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=8aa486160805280750q5a214961re21ed1dc731cf181@mail.gmail.com \
    --to=sbejar@gmail.com \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=victor@bogado.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 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 NNTP newsgroup(s).