From: David Woodhouse <dwmw2@infradead.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Robin Rosenberg <robin.rosenberg@dewire.com>, git@vger.kernel.org
Subject: Re: [JGIT PATCH 00/14] TreeWalk D/F conflict detection
Date: Tue, 19 Aug 2008 09:52:11 +0100 [thread overview]
Message-ID: <1219135931.3184.473.camel@pmac.infradead.org> (raw)
In-Reply-To: <1219103602-32222-1-git-send-email-spearce@spearce.org>
On Mon, 2008-08-18 at 16:53 -0700, Shawn O. Pearce wrote:
> This series is about fixing the "mistake" in Git trees where
> subtrees sort as through their name is "path/" and not "path".
Er, really? Does that mean this commit is broken, then?
http://git.kernel.org/?p=linux/kernel/git/dwmw2/misc-git-hacks.git;a=commitdiff;h=fc1b73da
I shouldn't need to know that -- I'd _really_ like a version of
'git-hash-object -t tree' which validates and sorts its input for me.
And maybe even takes input in _text_ form, so I don't have to convert
the sha1 to binary.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2008-08-19 8:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 23:53 [JGIT PATCH 00/14] TreeWalk D/F conflict detection Shawn O. Pearce
2008-08-18 23:53 ` [JGIT PATCH 01/14] Detect path names which overflow the name length field in the index Shawn O. Pearce
2008-08-18 23:53 ` [JGIT PATCH 02/14] Fix NB.decodeUInt16 to correctly handle the high byte Shawn O. Pearce
2008-08-18 23:53 ` [JGIT PATCH 03/14] Add test cases for NB.encode and NB.decode family of routines Shawn O. Pearce
2008-08-18 23:53 ` [JGIT PATCH 04/14] Fix DirCache's skip over null byte padding when reading a DIRC file Shawn O. Pearce
2008-08-18 23:53 ` [JGIT PATCH 05/14] Fix usage of assertEquals in DirCacheIteratorTest Shawn O. Pearce
2008-08-18 23:53 ` [JGIT PATCH 06/14] Refactor AbstractTreeIterator.pathCompare to force another mode Shawn O. Pearce
2008-08-18 23:53 ` [JGIT PATCH 07/14] Micro-optimize AbstractTreeIterator.pathCompare Shawn O. Pearce
2008-08-18 23:53 ` [JGIT PATCH 08/14] Optimize path comparsion within subtrees during TreeWalk Shawn O. Pearce
2008-08-18 23:53 ` [JGIT PATCH 09/14] Refactor AbstractTreeIterator semantics to start on first entry Shawn O. Pearce
2008-08-18 23:53 ` [JGIT PATCH 10/14] Make all AbstractTreeIterator implementations bi-directional Shawn O. Pearce
2008-08-18 23:53 ` [JGIT PATCH 11/14] Expose beginning of iterator indication from AbstractTreeIterator Shawn O. Pearce
2008-08-18 23:53 ` [JGIT PATCH 12/14] Allow application code to set ObjectIds in DirCacheEntry Shawn O. Pearce
2008-08-18 23:53 ` [JGIT PATCH 13/14] Create NameConflictTreeWalk to transparently detect D/F conflicts Shawn O. Pearce
2008-08-18 23:53 ` [JGIT PATCH 14/14] Add test case for NameConflictTreeWalk Shawn O. Pearce
2008-08-19 0:11 ` [JGIT PATCH 01/14] Detect path names which overflow the name length field in the index Junio C Hamano
2008-08-19 18:32 ` Robin Rosenberg
2008-08-19 19:57 ` Shawn O. Pearce
2008-08-19 8:52 ` David Woodhouse [this message]
2008-08-19 14:24 ` [JGIT PATCH 00/14] TreeWalk D/F conflict detection Shawn O. Pearce
-- strict thread matches above, loose matches on Subject: below --
2008-08-19 22:51 Shawn O. Pearce
2008-08-19 22:54 ` Shawn O. Pearce
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=1219135931.3184.473.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg@dewire.com \
--cc=spearce@spearce.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.
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).