path: root/builtin/merge-base.c
diff options
authorJeff King <>2016-10-12 20:10:40 (GMT)
committerJunio C Hamano <>2016-10-12 21:30:16 (GMT)
commit4f21454b55f4237b7d0487ad5099c9edf4fc3967 (patch)
tree823ab289135da04b10f02367e2e73777e83cb54f /builtin/merge-base.c
parent0b65a8dbdb38962e700ee16776a3042beb489060 (diff)
merge-base: handle --fork-point without reflog
The --fork-point option looks in the reflog to try to find where a derived branch forked from a base branch. However, if the reflog for the base branch is totally empty (as it commonly is right after cloning, which does not write a reflog entry), then our for_each_reflog call will not find any entries, and we will come up with no merge base, even though there may be one with the current tip of the base. We can fix this by just adding the current tip to our list of collected entries. Signed-off-by: Jeff King <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'builtin/merge-base.c')
1 files changed, 3 insertions, 0 deletions
diff --git a/builtin/merge-base.c b/builtin/merge-base.c
index c0d1822..b572a37 100644
--- a/builtin/merge-base.c
+++ b/builtin/merge-base.c
@@ -173,6 +173,9 @@ static int handle_fork_point(int argc, const char **argv)
revs.initial = 1;
for_each_reflog_ent(refname, collect_one_reflog_ent, &revs);
+ if (! && !get_sha1(refname, sha1))
+ add_one_commit(sha1, &revs);
for (i = 0; i <; i++)
revs.commit[i]->object.flags &= ~TMP_MARK;