git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org
Subject: Re: git-svn dcommit failure
Date: Thu, 07 Jun 2007 16:04:44 +0200	[thread overview]
Message-ID: <87abvb508z.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20070605101744.GA12948@muzzle> (Eric Wong's message of "Tue, 5 Jun 2007 03:17:44 -0700")

* Eric Wong:

>> After manually committing the offending changes via Subversion, I
>> git-svn has begun to work again, too (but I haven't yet tried to
>> change the same files).
>
> Would upgrading to 1.5.2 final have helped?

I've upgraded to this version, but since it's not exactly trivial for
me to test this on the Subversion side, it'll take some time until I
can be confident that the bug was indeed fixed in the
6442754d6cc0056cf5b69b43d218f8b6d317e7f5 revision.

Is there some kind of magic environment variable I could set to get
tracing information?  If such bugs turn up, I'd try to debug them on
my own and submit a fix, or at least a reproduction recipe.  (The
repository itself may contain personally identifiable information in
test cases and hence, cannot be shared.)

  reply	other threads:[~2007-06-07 14:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29  9:16 git-svn dcommit failure Florian Weimer
2007-05-29  9:35 ` Florian Weimer
     [not found]   ` <20070529144742.GG1025@.intersec.eu>
2007-05-29 15:20     ` Florian Weimer
2007-06-05 10:17       ` Eric Wong
2007-06-07 14:04         ` Florian Weimer [this message]
2007-06-09 20:05           ` Eric Wong
2007-06-09 20:22             ` Florian Weimer

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=87abvb508z.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --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).