From: "Chris Riddoch" <riddochc@gmail.com>
To: git@vger.kernel.org
Subject: Another fast-import/import-tars issue
Date: Fri, 11 May 2007 14:08:18 -0600 [thread overview]
Message-ID: <6efbd9b70705111308v47a76b04n9328ebf393a209e6@mail.gmail.com> (raw)
Hi, folks.
I believe I've uncovered an issue in fast-import, but I don't know the
code well enough yet to debug it. So, I'll produce my evidence and
let others work on finding the solution. It should be pretty easy to
reproduce.
First, I'm running: 1.5.2.rc1.9.g6644
Grab the tarball of Perl 5.8.8 - http://www.perl.com/CPAN/src/perl-5.8.8.tar.bz2
Note its md5, just so you know it's not corrupted from the outset.
b8c118d4360846829beb30b02a6b91a7 perl-5.8.8.tar.gz
a377c0c67ab43fd96eeec29ce19e8382 perl-5.8.8.tar.bz2
Try this:
$ tar -xjf perl-5.8.8.tar.bz2
$ cd perl-5.8.8
$ git init
$ git add .
$ git commit -a -m "Import from working tree copy"
Now, for convenience of debugging, I have myself a script I call
~/bin/fast-import-filter.sh:
#!/bin/bash
tee fast-import.log | git fast-import --quiet
Then, I have a slightly-changed ~/bin/import-tars script, like so:
20c20,21
< open(FI, '|-', 'git', 'fast-import', '--quiet')
---
> #open(FI, '|-', 'git', 'fast-import', '--quiet')
> open(FI, '|-', 'fast-import-filter.sh')
Now,
$ import-tars.pl ../perl-5.8.8.tar.bz2
Okay, so the trees pointed to by the tips of the master and
import-tars branches *should* be identical here, right?
$ git diff-tree master: import-tars: | wc -l
229
Not so good.
--
epistemological humility
Chris Riddoch
next reply other threads:[~2007-05-11 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 20:08 Chris Riddoch [this message]
2007-05-16 16:22 ` [PATCH] import-tars: Use the "Link indicator" to identify directories Johannes Schindelin
2007-05-16 18:24 ` Junio C Hamano
2007-05-16 18:49 ` Junio C Hamano
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=6efbd9b70705111308v47a76b04n9328ebf393a209e6@mail.gmail.com \
--to=riddochc@gmail.com \
--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).