All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: weigelt@metux.de, git@vger.kernel.org
Subject: Re: import determinism
Date: Sun, 07 Nov 2010 22:01:24 +0100	[thread overview]
Message-ID: <m2lj54u9uj.fsf@igel.home> (raw)
In-Reply-To: <AANLkTi=mx0AAKo2Asn5XJVcs30-PLuwhTbM=o0y36Wa_@mail.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Sun, 7 Nov 2010 21:46:57 +0100")

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

> On Sun, Nov 7, 2010 at 21:25, Enrico Weigelt <weigelt@metux.de> wrote:
>> I'm curious on how deterministic the imports (git-cvsimport and
>> git-svn) are. Suppose I close the same cvs repo twice (assuming
>> no write access in between), are the resulting object SHA-1's
>> the same ?
>
> No, because the committer dates will be different.

The committer info in every commit will be the same as the author info,
so the repository conversion is completely deterministic.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2010-11-07 21:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-07 20:25 import determinism Enrico Weigelt
2010-11-07 20:46 ` Ævar Arnfjörð Bjarmason
2010-11-07 21:01   ` Andreas Schwab [this message]
2010-11-07 21:56     ` Enrico Weigelt
2010-11-07 22:20     ` Martin Langhoff
2010-11-07 22:45       ` Andreas Schwab
2010-11-09 13:43         ` Enrico Weigelt
2010-11-10  4:40           ` Martin Langhoff
2010-11-10 16:18             ` Enrico Weigelt
2010-11-10 21:25               ` Martin Langhoff
2010-11-10 22:04                 ` Enrico Weigelt
2010-11-11  4:28           ` Michael Haggerty
2010-11-11 13:09             ` Enrico Weigelt

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=m2lj54u9uj.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=weigelt@metux.de \
    /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.