From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [BUG] git-svn: --no-metadata related bug
Date: Wed, 6 Apr 2011 23:42:39 +0530 [thread overview]
Message-ID: <20110406181234.GB667@kytes> (raw)
In-Reply-To: <4D9C64EB.5060703@drmicha.warpmail.net>
Hi Michael,
Michael J Gruber writes:
> Ramkumar Ramachandra venit, vidit, dixit 05.04.2011 21:07:
> > git svn clone --no-metadata -T trunk http://dxirc.googlecode.com/svn/
>
> Works fine for me, using:
>
> git svn --version
> git-svn version 1.7.5.rc0.365.g23929a (svn 1.6.16)
>
> What are the affected versions?
I'm sorry, but I have no additional information about the bug. I
simply reported it on someone else's behalf, hoping that someone on
the list would be able to reproduce it and supply a fix (see IRC
conversation and explanation for not being able to test it myself).
-- Ram
next prev parent reply other threads:[~2011-04-06 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 19:07 [BUG] git-svn: --no-metadata related bug Ramkumar Ramachandra
2011-04-06 13:04 ` Michael J Gruber
2011-04-06 18:12 ` Ramkumar Ramachandra [this message]
2011-09-03 7:01 ` DaveAbrahams
2011-09-07 3:39 ` 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=20110406181234.GB667@kytes \
--to=artagnon@gmail.com \
--cc=git@drmicha.warpmail.net \
--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).