summaryrefslogtreecommitdiff
path: root/list-objects.c
diff options
context:
space:
mode:
authorNguyễn Thái Ngọc Duy <pclouds@gmail.com>2013-08-16 16:52:06 +0700
committerJunio C Hamano <gitster@pobox.com>2013-08-28 11:54:18 -0700
commite76a5fb4593b80cdc9dda66809ae910e86b6ffbe (patch)
tree3223a109e5660fb0b321992921ffaa4e18e99c2b /list-objects.c
parentcdab485853b405d6454d4974bdc3825134d85249 (diff)
downloadgit-e76a5fb4593b80cdc9dda66809ae910e86b6ffbe.tar.gz
list-objects: reduce one argument in mark_edges_uninteresting
mark_edges_uninteresting() is always called with this form mark_edges_uninteresting(revs->commits, revs, ...); Remove the first argument and let mark_edges_uninteresting figure that out by itself. It helps answer the question "are this commit list and revs related in any way?" when looking at mark_edges_uninteresting implementation. Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'list-objects.c')
-rw-r--r--list-objects.c7
1 files changed, 3 insertions, 4 deletions
diff --git a/list-objects.c b/list-objects.c
index 3dd4a96019..db8ee4f04d 100644
--- a/list-objects.c
+++ b/list-objects.c
@@ -145,11 +145,10 @@ static void mark_edge_parents_uninteresting(struct commit *commit,
}
}
-void mark_edges_uninteresting(struct commit_list *list,
- struct rev_info *revs,
- show_edge_fn show_edge)
+void mark_edges_uninteresting(struct rev_info *revs, show_edge_fn show_edge)
{
- for ( ; list; list = list->next) {
+ struct commit_list *list;
+ for (list = revs->commits; list; list = list->next) {
struct commit *commit = list->item;
if (commit->object.flags & UNINTERESTING) {