From: Avery Pennarun <apenwarr@gmail.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Mihai Sucan <mihai.sucan@gmail.com>
Subject: Re: git svn errors out with git-cat-file "usage" message
Date: Wed, 29 Apr 2009 14:50:51 -0400 [thread overview]
Message-ID: <32541b130904291150k75a0433fnb29ea59f654a17f7@mail.gmail.com> (raw)
In-Reply-To: <46a038f90904290811p33332bd5h1d397734907ba9c2@mail.gmail.com>
On Wed, Apr 29, 2009 at 11:11 AM, Martin Langhoff
<martin.langhoff@gmail.com> wrote:
> Steps to repro, and error message:
>
> $ git svn clone -T trunk --ignore-paths releases
> http://paintweb.googlecode.com/svn paintweb.git
> r3 = 30548c9192aefcde23337f70542ab59e193a1b9e (trunk)
> usage: git-cat-file [-t|-s|-e|-p|<type>] <sha1>
> fatal: unable to run 'git-svn'
> $ git version
> git version 1.6.2.4.10.g2254d <== this is maint as of right now
>
> The same problem exists with master as of right now (v1.6.3-rc3-12-gb79376c)
I just tried this (commit 2254d) and was unable to reproduce; it
worked fine for me (Debian etch).
git svn clone -T trunk --ignore-paths releases
http://paintweb.googlecode.com/svn paintweb.git
...
r6 = 8561205fe08e0bcefb592710f4e34db91f3099df (trunk)
Checked out HEAD:
http://paintweb.googlecode.com/svn/trunk r6
Maybe you can try 'git bisect' to narrow it down.
Have fun,
Avery
next prev parent reply other threads:[~2009-04-29 18:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 15:11 git svn errors out with git-cat-file "usage" message Martin Langhoff
2009-04-29 18:50 ` Avery Pennarun [this message]
2009-04-29 20:25 ` Michael J Gruber
2009-04-29 20:47 ` Martin Langhoff
2009-04-29 21:05 ` Michael J Gruber
2009-04-30 7:18 ` Martin Langhoff
2009-04-30 7:53 ` Michael J Gruber
2009-04-30 8:26 ` Andreas Ericsson
2009-04-30 8:46 ` Michael J Gruber
2009-04-30 8:53 ` Martin Langhoff
2009-04-30 9:28 ` Michael J Gruber
2009-04-30 9:42 ` Martin Langhoff
2009-04-30 14:41 ` Avery Pennarun
2009-04-30 15:03 ` Martin Langhoff
2009-04-30 16:26 ` Avery Pennarun
2009-04-30 16:31 ` Martin Langhoff
2009-04-30 16:49 ` Michael J Gruber
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=32541b130904291150k75a0433fnb29ea59f654a17f7@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
--cc=mihai.sucan@gmail.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).