Allow AbstractTreeIterators to find out about StopWalkExceptions
commitf799b5d6b51c05ddfe7ed36ad4e3846506133a20
authorShawn O. Pearce <spearce@spearce.org>
Tue, 12 Aug 2008 01:07:52 +0000 (11 18:07 -0700)
committerRobin Rosenberg <robin.rosenberg@dewire.com>
Thu, 14 Aug 2008 17:33:19 +0000 (14 19:33 +0200)
tree87a4724e0eb002199591cf9a3a7e3a5a4498a00f
parent9ce42476d4a0fc6ef8b6693ad4be092e80172f31
Allow AbstractTreeIterators to find out about StopWalkExceptions

If a tree iterator has overridden skip() to specially handle entries
which the TreeWalk has decided are not relevant then it might also
need to pay attention to a StopWalkException.  The SWE is thrown out
of a filter and behaves much like skip, except it skips everything
else in the tree.  This is used by PathFilterGroup to break out of
a walk once we know that no additional records could ever match.

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/EmptyTreeIterator.java
org.spearce.jgit/src/org/spearce/jgit/treewalk/TreeWalk.java