From: Eric Wong <normalperson@yhbt.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Alec Berryman <alec@thened.net>
Subject: Re: [PATCH] git-svn: Always create a new RA when calling do_switch for svn://
Date: Wed, 17 Sep 2008 23:44:29 -0700 [thread overview]
Message-ID: <20080918064429.GB13328@untitled> (raw)
In-Reply-To: <1221426856-2652-1-git-send-email-alec@thened.net>
Alec Berryman <alec@thened.net> wrote:
>
> This was reported as Debian bug #464713. An example repository can be
> found at svn://svn.debian.org/chinese/packages/lunar-applet. When I try
> to clone it with 1.6.0.2.229.g1293c or 1.5.6.5, both using 1.5.1
> libraries, I see the following:
>
> r158 = 1107cff6309c979751e0841d40b9e2e471694b26 (git-svn@159)
> M debian/changelog
> M debian/rules
> r159 = 010d0b481753bd32ce0255ce433d63e14114d3b6 (git-svn@159)
> Found branch parent: (git-svn) 010d0b481753bd32ce0255ce433d63e14114d3b6
> Following parent with do_switch
> Malformed network data: Malformed network data at /home/alec/local/git/libexec/git-core//git-svn line 2360
>
> It looks like the user made several commits and decided to undo them by
> removing the directory and copying an older version in its place.
>
> This appears to only affect access via svn:// and svn+ssh://; I tried
> with file:// but not with http://.
>
> The first patch is a minor refactoring of some test code, and the second
> one actually fixes the issue for me.
Thanks Alec, and sorry for the latency.
This series is:
Acked-by: Eric Wong <normalperson@yhbt.net>
--
Eric Wong
prev parent reply other threads:[~2008-09-18 6:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-14 21:14 [PATCH] git-svn: Always create a new RA when calling do_switch for svn:// Alec Berryman
2008-09-14 21:14 ` [PATCH] git-svn: factor out svnserve test code for later use Alec Berryman
2008-09-14 21:14 ` [PATCH] git-svn: Always create a new RA when calling do_switch for svn:// Alec Berryman
2008-09-18 6:44 ` Eric Wong [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=20080918064429.GB13328@untitled \
--to=normalperson@yhbt.net \
--cc=alec@thened.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).