{"thread":{"id":"5781","subject":"[BUG] \"git cat-file tree <sha1>\" prints garbage","startedAt":"2006-10-01T20:26:02Z","lastAt":"2006-10-01T20:48:30Z","messageCount":2,"participants":["Sebastian Harl","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"28085","messageId":"20061001202602.GD32373@albany.tokkee.org","threadId":"5781","inReplyTo":null,"subject":"[BUG] \"git cat-file tree <sha1>\" prints garbage","fromName":"Sebastian Harl","fromEmail":"sh@tokkee.org","sentAt":"2006-10-01T20:26:02Z","receivedAt":"2006-10-01T20:26:02Z","isPatch":false,"sender":{"key":"sh@tokkee.org","avatar":"https://gravatar.com/avatar/c19b9c37bd63e5d1dabe8d222904921fb807d53d1d8d41af758a16c066eeb59c?d=mp&s=160"},"body":"Hi,\n\nWhen using \"git cat-file tree <sha1>\" to print a tree's content, it produces\ngarbage output like the following:\n\n  $ git cat-file -t c0cd1e4e1888be6a70d44476996ece8be1ab52a2\n  tree\n  $ git cat-file tree c0cd1e4e1888be6a70d44476996ece8be1ab52a2\n  100644 .gitignore%ëF7¦ùq¤¢«‚:“y—ǽ100644\n  COPYINGoø|Fd˜C—bW‘Èê;»_\"y£40000 DocumentationŠ>Ý¢ÞÀŸçœ $ë#ºâü100755\n  GIT-VERSION-GEN\n  [...]\n\nUsing \"git cat-file -p <sha1>\" works fine.\n(The above example uses one of the latest commits of the git.git repository)\n\nCheers,\nSebastian\n\n-- \nSebastian \"tokkee\" Harl\nGnuPG-ID: 0x8501C7FC\nhttp://tokkee.org/\n\n"},{"id":"28087","messageId":"Pine.LNX.4.63.0610012247330.14200@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"5781","inReplyTo":"20061001202602.GD32373@albany.tokkee.org","subject":"Re: [BUG] \"git cat-file tree <sha1>\" prints garbage","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2006-10-01T20:48:30Z","receivedAt":"2006-10-01T20:48:30Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sun, 1 Oct 2006, Sebastian Harl wrote:\n\n> When using \"git cat-file tree <sha1>\" to print a tree's content, it produces\n> garbage output like the following:\n> \n>   $ git cat-file -t c0cd1e4e1888be6a70d44476996ece8be1ab52a2\n>   tree\n>   $ git cat-file tree c0cd1e4e1888be6a70d44476996ece8be1ab52a2\n>   100644 .gitignore%ëF7¦ùq¤¢«‚:“y—ǽ100644\n>   COPYINGoø|Fd˜C—bW‘Èê;»_\"y£40000 DocumentationŠ>Ý¢ÞÀŸçœ $ë#ºâü100755\n>   GIT-VERSION-GEN\n>   [...]\n> \n> Using \"git cat-file -p <sha1>\" works fine.\n> (The above example uses one of the latest commits of the git.git repository)\n\nThat is not a bug. \"git cat-file tree <sha1>\" produces the _exact_ \ncontents of the object, while \"-p\" _pretty_-prints the contents.\n\nCiao,\nDscho\n"}]}