git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jay Soffian" <jaysoffian@gmail.com>
To: "Vladimir Pouzanov" <farcaller@gmail.com>
Cc: git@vger.kernel.org, "Eric Wong" <normalperson@yhbt.net>
Subject: Re: git-svn fails to fetch repository
Date: Wed, 14 Jan 2009 13:06:56 -0500	[thread overview]
Message-ID: <76718490901141006n6c70eb2cw67ad814b3739786e@mail.gmail.com> (raw)
In-Reply-To: <loom.20090114T083207-942@post.gmane.org>

On Wed, Jan 14, 2009 at 3:32 AM, Vladimir Pouzanov <farcaller@gmail.com> wrote:
> Jay Soffian <jaysoffian <at> gmail.com> writes:
>> So you're adding the "use Carp..." and "warn..." lines.
>>
>> Then try the import again. That should at least show why the svn_delta
>> temp file is being acquired twice.
>
> Output is pretty long so I've put in on pastebin:
> http://pastebin.com/m210be905

Okay, this is beyond me. git-svn (among other things) implements a
so-called delta editor (part of the subversion API). The driver for
that editor is apparently calling the editor's apply_textdelta()
method twice in a row w/o an intervening call to the editor's
close_file() method.

I don't understand when and/or why it would do this. This part of the
Subversion API seems not that well documented, and I got lost trying
to follow all the indirections in the Subversion source code (esp
w/the swig'ified Perl bindings). AFAICT, this should not be happening.

I could ask you to insert some more debugging statements to try to
track it to a specific file (or files), but I think at this point I'll
going to wait to see if the git-svn author has any ideas.

BTW, it doesn't help any that the order that files are checked out
seems not to be consistent. Not only is my git-svn clone working, the
order my files are checked out in is different from yours.

Oh, one other thing I don't understand is why the debugging output is
now showing that some files are being added for you (the lines
beginning with \tA). Before you weren't getting that. I had thought
these lines might be getting lost in stdout buffering, but git-svn
disables buffering on stdout, so color me confused.

Sorry I can't be more help,

j.

  reply	other threads:[~2009-01-14 18:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 14:53 git-svn fails to fetch repository Vladimir Pouzanov
2009-01-13 15:03 ` Vladimir Pouzanov
2009-01-13 17:51   ` Michael J Gruber
2009-01-13 19:01     ` Vladimir Pouzanov
2009-01-13 20:39       ` Björn Steinbrink
2009-01-13 20:46         ` Vladimir Pouzanov
2009-01-13 21:12           ` Jay Soffian
2009-01-13 21:16             ` Vladimir Pouzanov
2009-01-13 21:28               ` Jay Soffian
2009-01-13 21:34                 ` Vladimir Pouzanov
2009-01-13 21:46                   ` Jay Soffian
2009-01-14  0:58                   ` Jay Soffian
2009-01-14  8:32                     ` Vladimir Pouzanov
2009-01-14 18:06                       ` Jay Soffian [this message]
2009-01-17  9:51                         ` Eric Wong
2009-01-17 10:06                           ` Vladimir Pouzanov
2009-01-17 10:45                             ` Eric Wong
2009-01-17 17:33                               ` Jay Soffian
2009-01-13 21:20             ` Jay Soffian
2009-01-23  8:52           ` Petr Baudis
2009-01-23 13:22             ` Björn Steinbrink

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=76718490901141006n6c70eb2cw67ad814b3739786e@mail.gmail.com \
    --to=jaysoffian@gmail.com \
    --cc=farcaller@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=normalperson@yhbt.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).