From: Eric Wong <normalperson@yhbt.net>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: git@vger.kernel.org
Subject: Re: git-svn dcommit failure
Date: Tue, 5 Jun 2007 03:17:44 -0700 [thread overview]
Message-ID: <20070605101744.GA12948@muzzle> (raw)
In-Reply-To: <87k5ur64hx.fsf@mid.deneb.enyo.de>
Florian Weimer <fw@deneb.enyo.de> wrote:
> * Pierre Habouzit:
>
> > On Tue, May 29, 2007 at 11:35:10AM +0200, Florian Weimer wrote:
> >> * Florian Weimer:
> >>
> >> > This with git-svn 1.5.1.4-2 on something that is quite close to Debian
> >> > etch.
> >>
> >> Same issue with 1.5.2~rc3-2.
> >
> > Are you using ControlMaster in your ssh setup in auto/autoask mode? (I
> > assume your repository is svn+ssh). If yes, then you *have* to start a
> > persistent ssh connection before you do anything else:
>
> No. It's svn+ssh (with a custom connect script), but without the
> controlchan extension. Subversion works fine and lets me commit
> changes.
>
> 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?
Looking at 6442754d6cc0056cf5b69b43d218f8b6d317e7f5 (which was made
right before 1.5.2 final), the bug it fixed could've actually affected
modification-only commits, too.
If it's a public repository, could I look at the changeset that was
giving you trouble, and the [svn-remote] section of your .git/config
file? Thanks.
--
Eric Wong
next prev parent reply other threads:[~2007-06-05 10:17 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 [this message]
2007-06-07 14:04 ` Florian Weimer
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=20070605101744.GA12948@muzzle \
--to=normalperson@yhbt.net \
--cc=fw@deneb.enyo.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 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.