From: Sebastian Harl <sh@tokkee.org>
To: git@vger.kernel.org
Subject: [BUG] "git cat-file tree <sha1>" prints garbage
Date: Sun, 1 Oct 2006 22:26:02 +0200 [thread overview]
Message-ID: <20061001202602.GD32373@albany.tokkee.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
Hi,
When using "git cat-file tree <sha1>" to print a tree's content, it produces
garbage output like the following:
$ git cat-file -t c0cd1e4e1888be6a70d44476996ece8be1ab52a2
tree
$ git cat-file tree c0cd1e4e1888be6a70d44476996ece8be1ab52a2
100644 .gitignore%ëF7¦ùq¤¢«:yǽ100644
COPYINGoø|FdCbWÈê;»_"y£40000 Documentation>Ý¢ÞÀç $ë#ºâü100755
GIT-VERSION-GEN
[...]
Using "git cat-file -p <sha1>" works fine.
(The above example uses one of the latest commits of the git.git repository)
Cheers,
Sebastian
--
Sebastian "tokkee" Harl
GnuPG-ID: 0x8501C7FC
http://tokkee.org/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-10-01 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 20:26 Sebastian Harl [this message]
2006-10-01 20:48 ` [BUG] "git cat-file tree <sha1>" prints garbage Johannes Schindelin
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=20061001202602.GD32373@albany.tokkee.org \
--to=sh@tokkee.org \
--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