Chico Sokol <chico.so...@gmail.com> writes:
> 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:
Who wrote this commit object you are trying to read? Us, or your
library (this question is to see if you are chasing the right
> commit 191
> author Francisco Sokol <chico.so...@gmail.com> 1369140112 -0300
> committer Francisco Sokol <chico.so...@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?
If you care about the byte-for-byte compatibility, never use
"cat-file -p". That is meant for human consumption.
"git cat-file commit <sha1>" gives you the raw representation after
inflating and stripping out the first "<type> SP <length> LF" line.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html