git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Wolf <jw@raven.inka.de>
To: git@vger.kernel.org
Subject: Re: git-svn clone behaves non-deterministic
Date: Thu, 27 Nov 2008 23:40:42 +0100	[thread overview]
Message-ID: <20081127224042.GC12716@raven.wolf.lan> (raw)
In-Reply-To: <20081127182947.GB12716@raven.wolf.lan>

On Thu, Nov 27, 2008 at 07:29:47PM +0100, Josef Wolf wrote:

> - "HEAD points to unborn branch" confirms that the import failed
> - there are exactly 2000 "Checking reflog" lines.  Since the last
>   imported revision was 2008, I would have expected 2008 (or 2007
>   or 2009) such lines.  My first thought was this might be related
>   to the --repack option defaulting to 1000.  But with --repack=570
>   it also stops after r2008.

I've done lots of trial-and-error and I think I've finally found the
point where the script stops working.  Fortunately, git-svn is a perl
script :-). So I've found in the sub gs_do_update, the
statement

   $reporter->finish_report($pool);

is the last executed function.  Here is what Data::Dumper says about
the $pool parameter:

  $VAR1 = bless(
              do {
                  \(
                      my $o = bless(
                         do{
                              \(my $o = 148559280)
                         },
                         '_p_apr_pool_t'
                      )
                   )
              },
              'SVN::Pool'
          );

I have tried to format the Data::Dumper output more readable.

Any hints how to get closer to the problem?

      reply	other threads:[~2008-11-27 22:51 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
2008-11-27 18:29   ` Josef Wolf
2008-11-27 22:40     ` Josef Wolf [this message]

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=20081127224042.GC12716@raven.wolf.lan \
    --to=jw@raven.inka.de \
    --cc=git@vger.kernel.org \
    /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).