git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Josef Wolf <jw@raven.inka.de>, git@vger.kernel.org
Subject: Re: git-svn clone behaves non-deterministic
Date: Thu, 27 Nov 2008 10:55:12 +0100	[thread overview]
Message-ID: <492E6E80.7010209@drmicha.warpmail.net> (raw)
In-Reply-To: <20081127075351.GA12716@raven.wolf.lan>

Josef Wolf venit, vidit, dixit 27.11.2008 08:53:
> Hello,
> 
> I am new to git and decided to get my feet wet by first cloning and
> playing with my existing svn repositories.  Thus, I've done this:
> 
>  cd /my/test/repos
>  for i in repo1 repo2 repo3; do
>    repos=https://my.repos.server/repos/$i/trunk
>    svn co        $repos svn/$i
>    git-svn clone $repos git/$i
>  done
> 
>  for i in `cd svn; echo *`; do diff --exclude /.svn -Nruw */$i; done
> 
> With this, I see that four of the repositories are cloned as expected,
> but the fifth has only the .git directory in it.  It appears that
> the clone command stopped cloning at r2008, while the repository is
> currently at r3761.  So almost the half of the history was not
> cloned at all.  I've investigated the offending revision and the
> revisions around it, but I can't see anything special about them.
> The effect is perfectly reproducible and it stops always on the very
> same revision.  I get no error message at all.  I've attached the
> last lines of the clone operation at the end of this mail.

First of all: What does git --version say? Is it self-compiled git or
git as it comes with U 8.10?

Then: I assume the above is not quite what you did, otherwise I would be
surprised you see a 4th and 5th clone...

Your repo is probably one giant svn repo. In any case, the fact that the
repo is at $rev does not imply that the last commit on trunk is at $rev.
 What is the last commit on trunk?

Other than that: There are so many sins you can commit (!) in an svn
repo that it it is hard to tell which one threw git-svn off. Can you
share the repo?

> Then I go to another machine and enter exactly the same commands as
> above.  Both machines are fresh ubuntu-8.10 default installs.
> 
> To my surprise, on this other machine the clone operation seems to
> have worked for all the repositories.  But the diff command shows
> me that arbitrary files are missing in _all_ of the repositories.

I don't think computers behave deterministically, at least not according
to my experience. After all they rely on quantum mechanics, and who has
ever understood the measurement process, the collapsing of the wave
function?

OK: Whenever I got 2 different results after doing the same twice I
found that indeed some hidden/forgotten variable was not the same... Any
chance you find one?

Michael

  reply	other threads:[~2008-11-27  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27  7:53 git-svn clone behaves non-deterministic Josef Wolf
2008-11-27  9:55 ` Michael J Gruber [this message]
2008-11-27 18:29   ` Josef Wolf
2008-11-27 22:40     ` Josef Wolf

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=492E6E80.7010209@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=jw@raven.inka.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 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).