From: Jonathan Nieder <jrnieder@gmail.com>
To: Andreas Stricker <astricker@futurelab.ch>
Cc: Benjamin Pabst <benjamin.pabst85@gmail.com>, git@vger.kernel.org
Subject: Re: Fwd: Error with git-svn pushing a rename
Date: Fri, 15 Nov 2013 14:53:16 -0800 [thread overview]
Message-ID: <20131115225316.GF27781@google.com> (raw)
In-Reply-To: <5286235D.9060602@futurelab.ch>
Andreas Stricker wrote:
> svn, Version 1.7.10 (r1485443)
>
> I tried to reproduce the problem with git version 1.8.4.2 and
> Subversion version 1.8.4 (r1534716) with a fresh and pristine
> subversion repo and a git-svn clone of it: I didn't manage to
> reproduce the rename issue. Then I switched subversion back to
> 1.7.10, created both the repo and the git-svn clone, switched
> againt to 1.8.4.2 and then got an error. Unfortunately I didn't
> check if the subversion perlbindings were regenerated, so I'm
> not exactly sure.
[...]
> It looks like a fresh git svn clone may fix the problem.
Yuck.
Can you give an exact sequence of steps (including "Upgrade Subversion
at this step") to reproduce the problem? That would help immensely
--- if at all possible, I would very much like to keep existing
git-svn repos working on upgrade.
Thanks for your work so far on this.
Sincerely,
Jonathan
next prev parent reply other threads:[~2013-11-15 22:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAM-uYMgy8duxdGY8rbCJv9To3FFMAUDv22nnzbQ+e3QrTCLLpQ@mail.gmail.com>
[not found] ` <CAM-uYMigCTK=j3HkyT0F=jtDoDERdtkpZiTXRvBhSHJW3edJ-w@mail.gmail.com>
2013-11-14 15:26 ` Fwd: Error with git-svn pushing a rename Benjamin Pabst
2013-11-15 7:34 ` Andreas Stricker
[not found] ` <CAM-uYMgn4SGqurqRG-RDiicLxpf9NfTPUvNn9FaFUUbxFRJsZw@mail.gmail.com>
2013-11-15 13:36 ` Andreas Stricker
2013-11-15 22:53 ` Jonathan Nieder [this message]
2013-11-17 22:55 ` Andreas Stricker
2013-11-20 22:10 ` Benjamin Pabst
2013-12-24 21:11 ` Roman Kagan
2013-12-25 10:52 ` Roman Kagan
2013-12-25 13:13 ` Roman Kagan
2013-12-25 16:31 ` Thomas Rast
2013-12-26 12:05 ` [PATCH] git-svn: workaround for a bug in svn serf backend Roman Kagan
2013-12-26 20:28 ` Jonathan Nieder
2013-12-27 6:09 ` Roman Kagan
2013-12-27 7:52 ` Roman Kagan
2013-12-27 8:05 ` [PATCH v2] " Roman Kagan
2013-12-27 20:07 ` Jonathan Nieder
2013-12-27 20:34 ` Eric Wong
2013-12-27 22:22 ` Junio C Hamano
2013-12-28 9:58 ` Roman Kagan
2013-12-30 19:44 ` Junio C Hamano
2013-12-31 7:20 ` Roman Kagan
2014-01-17 11:32 ` Roman Kagan
2014-01-17 19:23 ` Junio C Hamano
2014-01-06 15:51 ` Andreas Stricker
2013-12-30 12:20 ` [PATCH] " Thomas Rast
2013-12-30 16:01 ` Roman Kagan
2013-11-18 17:59 ` Fwd: Error with git-svn pushing a rename Benjamin Pabst
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=20131115225316.GF27781@google.com \
--to=jrnieder@gmail.com \
--cc=astricker@futurelab.ch \
--cc=benjamin.pabst85@gmail.com \
--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).