Torgil Svensson wrote: > On 12/16/06, Torgil Svensson <torgil.svensson@xxxxxxxxx> wrote: >> >> example tree object: >> >> 100644 blob <sha1 of blob> README >> 100644 blob <sha1 of blob> REPORTING-BUGS >> 100644 link <sha1 of blob> <sha1 of commit> >> 040000 tree <sha1 of tree> arch >> 040000 tree <sha1 of tree> block >> 040000 link <sha1 of tree> <sha1 of commit> >> > > Sorry, I was sloppy and forgot the names: > > 100644 blob <sha1 of blob> README > 100644 blob <sha1 of blob> REPORTING-BUGS > 100644 link <sha1 of blob> <sha1 of commit> AUTHORS > 040000 tree <sha1 of tree> arch > 040000 tree <sha1 of tree> block > 040000 link <sha1 of tree> <sha1 of commit> misc > > Now it doesn't looks like trees/blobs anymore so maybe a link object > is handy: > > 100644 blob <sha1 of blob> README > 100644 blob <sha1 of blob> REPORTING-BUGS > 100644 link <sha1 of link> AUTHORS > 040000 tree <sha1 of tree> arch > 040000 tree <sha1 of tree> block > 040000 link <sha1 of link> misc > > link-object: > <sha1 of commit> > <sha1 of tree/blob> What do you need <sha1 of tree/blob> for in link-object? Wouldn't you use usually the sha1 of top tree of a commit, which is uniquely defined by commit object, so you need only <ahs1 of commit>? -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html