From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Joshua N Pritikin <jpritikin@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: problem with import-tars?
Date: Mon, 21 May 2007 14:43:33 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705211441310.6410@racer.site> (raw)
In-Reply-To: <20070521084846.GN11652@always.joy.eth.net>
Hi,
On Mon, 21 May 2007, Joshua N Pritikin wrote:
> I ran the import-tars which comes with 1:1.5.1.1-1 (Debian). I checked
> out the import-tars branch but now I can't commit:
>
> [...]
I think that the bug you experienced is solved in 1.5.2. You can download
import-tars.perl separately, as it should work with the 1.5.1.1 plumbing:
http://repo.or.cz/w/git.git?a=blob;f=contrib/fast-import/import-tars.perl;h=23aeb257b9557cb146586868084ce1b20d7e7ac8;hb=HEAD
Hth,
Dscho
next prev parent reply other threads:[~2007-05-21 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 8:48 problem with import-tars? Joshua N Pritikin
2007-05-21 13:43 ` Johannes Schindelin [this message]
2007-05-22 6:42 ` Joshua N Pritikin
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=Pine.LNX.4.64.0705211441310.6410@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jpritikin@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).