Fix uninteresting tags in new revision parsing

Fix uninteresting tags in new revision parsing

[Linus Torvalds]

When I unified the revision argument parsing, I introduced a simple bug 
wrt tags that had been marked uninteresting. When it was preparing for the 
revision walk, it would mark all the parent commits of an uninteresting 
tag correctly uninteresting, but it would forget about the commit itself.

This means that when I just did my 2.6.17-rc2 release, and my scripts 
generated the log for "v2.6.17-rc1..v2.6.17-rc2", everything was fine, 
except the commit pointed to by 2.6.17-rc1 (which shouldn't have been 
there) was included. Even though it should obviously have been marked as 
being uninteresting.

Not a huge deal, and the fix is trivial.

Signed-off-by: Linus Torvalds <torvalds@osdl.org>
---
diff --git a/revision.c b/revision.c
index dbd54da..113dd5a 100644
--- a/revision.c
+++ b/revision.c
@@ -152,6 +152,7 @@ static struct commit *handle_commit(stru
 		if (parse_commit(commit) < 0)
 			die("unable to parse commit %s", name);
 		if (flags & UNINTERESTING) {
+			commit->object.flags |= UNINTERESTING;
 			mark_parents_uninteresting(commit);
 			revs->limited = 1;
 		}

Re: Fix uninteresting tags in new revision parsing

[Junio C Hamano]

Linus Torvalds <torvalds@osdl.org> writes:

> When I unified the revision argument parsing, I introduced a simple bug 
> wrt tags that had been marked uninteresting. When it was preparing for the 
> revision walk, it would mark all the parent commits of an uninteresting 
> tag correctly uninteresting, but it would forget about the commit itself.

Thanks.  Can't believe I missed it...