mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Chico Sokol <>
To: Jakub Narebski <>
Cc: git <>
Subject: Re: Exact format of tree objets
Date: Tue, 18 Jun 2013 10:53:29 -0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


By the way, where can I find this kind of specification? I couldn't
find the spec of tree objects here:

Chico Sokol

On Wed, Jun 12, 2013 at 11:06 AM, Jakub Narebski <> wrote:
> Junio C Hamano <gitster <at>> writes:
>> Chico Sokol <chico.sokol <at>> writes:
>> > Is there any official documentation of tree objets format? Are tree
>> > objects encoded specially in some way? How can I parse the inflated
>> > contents of a tree object?
>> >
>> > We're suspecting that there is some kind of special format or
>> > encoding, because the command "git cat-file -p <sha>" show me ...
>> > While "git cat-file tree <sha>" generate ...
>> "cat-file -p" is meant to be human-readable form.  The latter gives
>> the exact byte contents read_sha1_file() sees, which is a binary
>> format.  Essentially, it is a sequence of:
>>  - mode of the entry encoded in octal, without any leading '0' pad;
>>  - pathname component of the entry, terminated with NUL;
>>  - 20-byte SHA-1 object name.
> I always wondered why this is the sole object format where SHA-1 is in 20-
> byte binary format and not 40-chars hexadecimal string format...
> --
> Jakub Narębski
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to
> More majordomo info at

      reply	other threads:[~2013-06-18 13:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 16:25 Exact format of tree objets Chico Sokol
2013-06-11 18:26 ` Ilari Liusvaara
2013-06-18 15:15   ` Chico Sokol
2013-06-18 17:47     ` Thomas Rast
2013-06-11 18:38 ` Junio C Hamano
2013-06-12 14:06   ` Jakub Narebski
2013-06-18 13:53     ` Chico Sokol [this message]

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).