From: Eric Wong <normalperson@yhbt.net>
To: Hin-Tak Leung <htl10@users.sourceforge.net>
Cc: git@vger.kernel.org, stoklund@2pi.dk, fabian.schmied@gmail.com,
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 21:42:17 +0000 [thread overview]
Message-ID: <20141031214217.GA15591@dcvr.yhbt.net> (raw)
In-Reply-To: <1414789740.30576.BPMail_high_carrier@web172302.mail.ir2.yahoo.com>
Hin-Tak Leung <htl10@users.sourceforge.net> wrote:
> On Fri, Oct 31, 2014 19:08 GMT Eric Wong wrote:
> >Filed a bug in Debian since I hit it in sid, too:
> >http://bugs.debian.org/767530
> >
> >Thanks all.
>
> Hmm, but why are you filing at debian? I had the error when i applied
> the dev code patches on top of 2.1.0, and the error disappeared as
> soon as I reverted the patches. So it looks like a issue for the
> upstream developers, rather than distro. Are you saying debian is
> shipping a dev snapshot of git svn?
I don't track SVN upstream development, so haven't checked if it affects
newer SVN, yet. It is the distro maintainer's job to get this resolved.
This bug affects existing cases of "git svn show-ignore",
we just happened to find it with "git svn fetch", first.
Debian's bug tracker also has the lowest barrier to entry:
no login/registration is necessary (just like this git list).
If you want to handle this with upstream directly, please do.
I try to avoid logins/accounts as much as possible.
next prev parent reply other threads:[~2014-10-31 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 21:09 [PATCH v2] git-svn: use SVN::Ra::get_dir2 when possible Hin-Tak Leung
2014-10-31 21:42 ` Eric Wong [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-31 21:53 Hin-Tak Leung
2014-10-31 23:22 ` Eric Wong
2014-11-01 2:19 ` Hin-Tak Leung
2014-11-01 3:13 ` Eric Wong
2014-11-01 6:13 ` Hin-Tak Leung
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=20141031214217.GA15591@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