Notify AbstractTreeIterator implementations of skipped tree entries
commitcbe13b151906abde49cf16b63b4d50eabf1d4090
authorShawn O. Pearce <spearce@spearce.org>
Sun, 10 Aug 2008 08:46:18 +0000 (10 01:46 -0700)
committerRobin Rosenberg <robin.rosenberg@dewire.com>
Wed, 13 Aug 2008 19:55:55 +0000 (13 21:55 +0200)
treeb2e6e6d07421a576b513d172f7a5a4fca6f0d7df
parent5b07a80cfdf506eb8aa36ca5e5356a336d303dd5
Notify AbstractTreeIterator implementations of skipped tree entries

Some tree iterators may benefit from knowing when their driving TreeWalk
has chosen to skip past their current entry and not report it to client
applications.  This can be useful for an index update scenario where the
client application has applied a TreeFilter to only see the entries that
it wants to modify in this session.

By default the new skip() method just calls next(), as most types of the
tree iterator do not have this distinction between skipped entry and a
non-skipped entry.

Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>
org.spearce.jgit/src/org/spearce/jgit/treewalk/AbstractTreeIterator.java
org.spearce.jgit/src/org/spearce/jgit/treewalk/TreeWalk.java