From: Shawn Pearce <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: A Large Angry SCM <gitzilla@gmail.com>, git@vger.kernel.org
Subject: Re: Git files data formats documentation
Date: Sat, 5 Aug 2006 15:30:46 -0400 [thread overview]
Message-ID: <20060805193046.GA20565@spearce.org> (raw)
In-Reply-To: <7vac6jfzem.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> Not quite. An entry for a subtree is sorted as if a '/' is
> suffixed to its name.
>
> $ git ls-tree $T
> 100644 blob 2398e9f8892812607f5eee6ed0d5712c2e3de197 a-
> 100644 blob 7f07527a80bd8c2b1c5087d7ccfe61073b068374 a-b
> 040000 tree 23fddf6a57ff3ba98aa93fb71431276c3f1a3c40 a
> 100644 blob 2afe6dcc5466068b8dcc7263cece05d2adf044fe a=
> 100644 blob efc73add7dd868242a66faf2a59b145f2a60b834 a=b
>
> This is, by the way, consistent with the order of cache entries
> in the index file.
Arrrrgh. I didn't realize that '/' was needed on the end of a tree
name when sorting its parent for output. jgit was/is definately
doing this wrong. And it all comes back to how the index operates,
doesn't it? :-)
I've got to go back now and do some surgery on how jgit sorts
entries in a tree. Clearly it would be incorrect with the example
you just gave. It also would have thought that core GIT generated
a corrupt tree if it tried to read in your example. Thank you for
taking the time to clarify it!
--
Shawn.
next prev parent reply other threads:[~2006-08-05 19:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 5:39 Git files data formats documentation A Large Angry SCM
2006-08-05 5:48 ` Jon Smirl
2006-08-05 6:51 ` Junio C Hamano
2006-08-05 19:30 ` Shawn Pearce [this message]
2006-08-05 21:56 ` A Large Angry SCM
2006-08-06 0:37 ` Junio C Hamano
2006-08-05 16:22 ` Shawn Pearce
2006-08-05 17:31 ` A Large Angry SCM
2006-08-05 18:41 ` Jakub Narebski
2006-08-05 20:15 ` A Large Angry SCM
2006-08-05 23:43 ` Jakub Narebski
2006-08-05 22:35 ` A Large Angry SCM
2006-08-16 16:55 ` Nicolas Pitre
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060805193046.GA20565@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitzilla@gmail.com \
--cc=junkio@cox.net \
/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.
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 NNTP newsgroup(s).