From: "Shawn O. Pearce" <spearce@spearce.org>
To: Robin Rosenberg <robin.rosenberg@dewire.com>
Cc: git@vger.kernel.org
Subject: Re: [JGIT PATCH 00/14] TreeWalk D/F conflict detection
Date: Tue, 19 Aug 2008 15:54:03 -0700 [thread overview]
Message-ID: <20080819225403.GG24212@spearce.org> (raw)
In-Reply-To: <1219186314-24048-1-git-send-email-spearce@spearce.org>
Sorry about that, my git-send-email directory had this cover letter
laying around in it from last time. There is no series, I only meant
to post the single patch "Support path names longer than 4095...".
> Shawn O. Pearce (14):
> Detect path names which overflow the name length field in the index
> Fix NB.decodeUInt16 to correctly handle the high byte
> Add test cases for NB.encode and NB.decode family of routines
> Fix DirCache's skip over null byte padding when reading a DIRC file
> Fix usage of assertEquals in DirCacheIteratorTest
> Refactor AbstractTreeIterator.pathCompare to force another mode
> Micro-optimize AbstractTreeIterator.pathCompare
> Optimize path comparsion within subtrees during TreeWalk
> Refactor AbstractTreeIterator semantics to start on first entry
> Make all AbstractTreeIterator implementations bi-directional
> Expose beginning of iterator indication from AbstractTreeIterator
> Allow application code to set ObjectIds in DirCacheEntry
> Create NameConflictTreeWalk to transparently detect D/F conflicts
> Add test case for NameConflictTreeWalk
...
> 18 files changed, 1418 insertions(+), 207 deletions(-)
--
Shawn.
next prev parent reply other threads:[~2008-08-19 22:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 22:51 [JGIT PATCH 00/14] TreeWalk D/F conflict detection Shawn O. Pearce
2008-08-19 22:51 ` [JGIT PATCH] Support path names longer than 4095 bytes in DirCache Shawn O. Pearce
2008-08-19 22:54 ` Shawn O. Pearce [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-18 23:53 [JGIT PATCH 00/14] TreeWalk D/F conflict detection Shawn O. Pearce
2008-08-19 8:52 ` David Woodhouse
2008-08-19 14:24 ` 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=20080819225403.GG24212@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg@dewire.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.