From: Eric Wong <normalperson@yhbt.net>
To: Hin-Tak Leung <htl10@users.sourceforge.net>
Cc: stoklund@2pi.dk, fabian.schmied@gmail.com, git@vger.kernel.org,
sam@vilain.net, stevenrwalter@gmail.com, waste.manager@gmx.de,
amyrick@apple.com
Subject: Re: [PATCH v2] git-svn: use SVN::Ra::get_dir2 when possible
Date: Fri, 31 Oct 2014 23:22:22 +0000 [thread overview]
Message-ID: <20141031232222.GA30046@dcvr.yhbt.net> (raw)
In-Reply-To: <1414792434.54806.YahooMailBasic@web172304.mail.ir2.yahoo.com>
Hin-Tak Leung <htl10@users.sourceforge.net> wrote:
> Tested-by: Hin-Tak Leung <htl10@users.sourceforge.net>
>
> Okay, this one on top of my "git 2.1.0 + 10 recent git svn improvement patches"
> allow me to fetch further.
>
> I suspect the problem must be elsewhere though, and this just band-aided
> over it.
>
> For me, reverting the additional patches and just use git 2.1.0 also allow
> me to fetch further, so the problem appear to me to be associated with
> the additional patches.
Junio already pulled all of those git-svn patches into git 2.2.0-rc0:
http://mid.gmane.org/xmqq7fzgt0q4.fsf@gitster.dls.corp.google.com
Can you give that a try? I've been able to complete the vbox
fetch without problems.
> But you are saying that git-svn on debian as shipped
> exhibit this problem?
No, I'm saying unrelated, (old) functionality such as
"git svn show-ignore" also got broken by this SVN bug.
next prev parent reply other threads:[~2014-10-31 23:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 21:53 [PATCH v2] git-svn: use SVN::Ra::get_dir2 when possible Hin-Tak Leung
2014-10-31 23:22 ` Eric Wong [this message]
2014-11-01 2:19 ` Hin-Tak Leung
2014-11-01 3:13 ` Eric Wong
2014-11-01 6:13 ` Hin-Tak Leung
-- strict thread matches above, loose matches on Subject: below --
2014-10-31 21:09 Hin-Tak Leung
2014-10-31 21:42 ` Eric Wong
2014-10-31 10:15 [PATCH] " Eric Wong
2014-10-31 10:34 ` [PATCH v2] " Eric Wong
2014-10-31 19:08 ` Eric Wong
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=20141031232222.GA30046@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=amyrick@apple.com \
--cc=fabian.schmied@gmail.com \
--cc=git@vger.kernel.org \
--cc=htl10@users.sourceforge.net \
--cc=sam@vilain.net \
--cc=stevenrwalter@gmail.com \
--cc=stoklund@2pi.dk \
--cc=waste.manager@gmx.de \
/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