[PATCH] bisect: use "clear_commit_marks" after checking ancestors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



instead of "unparse_commit", as it is enough to just clear flags.

Signed-off-by: Christian Couder <chriscool@xxxxxxxxxxxxx>
---
 bisect.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

	As the patch series where "unparse_commit" is added and
	used is already in "next". Here is a patch to use
	"clear_commit_marks" instead. The patch that adds
	"unparse_commit" can be reverted from "next" after this
	one.

diff --git a/bisect.c b/bisect.c
index c43c120..18f9fa4 100644
--- a/bisect.c
+++ b/bisect.c
@@ -771,7 +771,7 @@ static int check_ancestors(const char *prefix)
 	/* Clean up objects used, as they will be reused. */
 	for (i = 0; i < pending_copy.nr; i++) {
 		struct object *o = pending_copy.objects[i].item;
-		unparse_commit((struct commit *)o);
+		clear_commit_marks((struct commit *)o, ALL_REV_FLAGS);
 	}
 
 	return res;
-- 
1.6.3.GIT

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]