| commit | 1d627b30e61439aadcd303f8d9f3994e2ff94a77 | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Wed, 14 May 2008 03:19:34 +0000 (13 23:19 -0400) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Sat, 17 May 2008 03:59:49 +0000 (16 23:59 -0400) | ||
| tree | fe710bfdd06dade8617ef220233835f0321e753d | treesnapshot (tar.gz zip) |
| parent | e319780a6a7da6b42ad35d58754e26261d714fc7 | commitdiff |
Allow RevWalk's flag carrying behavior to be overridden
Some applications may need to carry flags not just onto the parents
of a commit, but also onto the tree and its referenced subtrees and
blobs. Doing this can be expensive, so we only want to pay such a
penalty if full object tracking has been enabled/requested by the
application code. By redirecting this carry logic into RevWalk we
permit it to be overridden by a specialized RevWalk subclass.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Some applications may need to carry flags not just onto the parents
of a commit, but also onto the tree and its referenced subtrees and
blobs. Doing this can be expensive, so we only want to pay such a
penalty if full object tracking has been enabled/requested by the
application code. By redirecting this carry logic into RevWalk we
permit it to be overridden by a specialized RevWalk subclass.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>