git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joshua N Pritikin <jpritikin@pobox.com>
To: git@vger.kernel.org
Subject: problem with import-tars?
Date: Mon, 21 May 2007 14:18:46 +0530	[thread overview]
Message-ID: <20070521084846.GN11652@always.joy.eth.net> (raw)

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:

joshua@emit:~/ev$ git commit
error: unable to read tree object HEAD
# On branch import-tars
error: unable to read tree object HEAD
[...snip...]

joshua@emit:~/ev$ git fsck-objects --full
warning in tree 05c3fd86565c57f128495d420565f813ba4b2535: contains empty 
pathname
warning in tree 16f235c9367ca15e3a3a6709547e235f701a1ee5: contains empty 
pathname
warning in tree 30f1e3c3926c52094bf6bb182906feed0cad2da1: contains empty 
pathname
warning in tree 528e0a55edc527f8f8a14d33057a6003ec87071d: contains empty 
pathname
warning in tree 5818056708134bbd4217195b32c65feed0527547: contains empty 
pathname
warning in tree 75382de0c9f403cb2c72e56b255a617c43bcd679: contains empty 
pathname
warning in tree a66bbc0c86757d18f187079d1f25bbaea19fc29c: contains empty 
pathname
warning in tree aa17744c47e7b8898e956b8d8e246f8b0b9860d8: contains empty 
pathname
warning in tree b120f845d24d7736aab58f04745c03a54366d68f: contains empty 
pathname
warning in tree eb650564f413d4a3fb67ca5f0c4e8dac08262f52: contains empty 
pathname

How do I proceed? I upgraded to 1:1.5.1.4-2 but the problem persists.

-- 
Make April 15 just another day, visit http://fairtax.org

             reply	other threads:[~2007-05-21  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21  8:48 Joshua N Pritikin [this message]
2007-05-21 13:43 ` problem with import-tars? Johannes Schindelin
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=20070521084846.GN11652@always.joy.eth.net \
    --to=jpritikin@pobox.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).