[PATCH] Prevent git-rev-list without --merge-order producing duplicates in output
commit51b1e1713b1ed8e962e994cd0850ea439ad8c3de
authorJon Seymour <jon.seymour@gmail.com>
Mon, 20 Jun 2005 02:29:38 +0000 (20 12:29 +1000)
committerLinus Torvalds <torvalds@ppc970.osdl.org>
Mon, 20 Jun 2005 03:13:18 +0000 (19 20:13 -0700)
tree1887c012ec509096a8be45a5bc2c7ea43590eaf9
parenteff19d5eccd02341a25f1543ff89fa7351163e3f
[PATCH] Prevent git-rev-list without --merge-order producing duplicates in output

If b is reachable from a, then:

 git-rev-list a b

argument would print one of the commits twice.

This patch fixes that problem. A previous problem fixed it for the
--merge-order switch.

Signed-off-by: Jon Seymour <jon.seymour@gmail.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
epoch.h
rev-list.c