From: Felipe Contreras <felipe.contreras@gmail.com>
To: Chico Sokol <chico.sokol@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Reading commit objects
Date: Tue, 21 May 2013 16:25:51 -0500 [thread overview]
Message-ID: <CAMP44s2YLK=EQ+YGh5s9HLGAtgvtNvgDdmXMPpw+PRbODD08RQ@mail.gmail.com> (raw)
In-Reply-To: <CABx5MBQ57-=MPamvV-peZUdD_KDLX+5cy9vD7CL7p_Vz9BkvTg@mail.gmail.com>
On Tue, May 21, 2013 at 4:21 PM, Chico Sokol <chico.sokol@gmail.com> wrote:
> Hello,
>
> I'm building a library to manipulate git repositories (interacting
> directly with the filesystem).
>
> Currently, we're trying to parse commit objects. After decompressing
> the contents of a commit object file we got the following output:
>
> commit 191
> author Francisco Sokol <chico.sokol@gmail.com> 1369140112 -0300
> committer Francisco Sokol <chico.sokol@gmail.com> 1369140112 -0300
>
> first commit
>
> We hoped to get the same output of a "git cat-file -p <sha1>", but
> that didn't happened. From a commit object, how can I find tree object
> hash of this commit?
git rev-parse <sha1>:
--
Felipe Contreras
next prev parent reply other threads:[~2013-05-21 21:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 21:21 Reading commit objects Chico Sokol
2013-05-21 21:25 ` Felipe Contreras [this message]
2013-05-21 21:37 ` John Szakmeister
2013-05-21 22:18 ` Chico Sokol
2013-05-21 22:22 ` Junio C Hamano
2013-05-21 22:33 ` Chico Sokol
2013-05-21 23:34 ` Jonathan Nieder
2013-05-22 5:54 ` Shawn Pearce
2013-05-22 4:51 ` java zlib woes (was: Reading commit objects) Andreas Krey
2013-05-22 5:56 ` Shawn Pearce
2013-05-27 4:11 ` Andreas Krey
2013-06-04 10:18 ` fetch delta resolution vs. checkout (was: java zlib woes) Andreas Krey
2013-05-22 5:59 ` Reading commit objects Shawn Pearce
2013-05-22 14:20 ` Chico Sokol
2013-05-22 20:02 ` Shawn Pearce
2013-05-22 14:25 ` Chico Sokol
2013-05-22 14:47 ` Chico Sokol
2013-05-22 19:59 ` Shawn Pearce
2013-05-21 22:20 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMP44s2YLK=EQ+YGh5s9HLGAtgvtNvgDdmXMPpw+PRbODD08RQ@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=chico.sokol@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).