projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 15000d7) | patch
Do a very simple "merge-base" that finds the most recent common
authorLinus Torvalds <torvalds@ppc970.osdl.org>
Sun, 17 Apr 2005 19:18:17 +0000 (12:18 -0700)
committerLinus Torvalds <torvalds@ppc970.osdl.org>
Sun, 17 Apr 2005 19:18:17 +0000 (12:18 -0700)
commit6683463ed6b2da9eed309c305806f9393d1ae728
tree6d296ca7b9d8916797835771722b0c46085a6ea4tree | snapshot
parent15000d78996db926d18dd68e6f5f5770de09cad3commit | diff
Do a very simple "merge-base" that finds the most recent common
parent of two commits.

The question of "best" commit can probably be tweaked almost arbitrarily.
In particular, trying to take things like how big the tree differences
are into account migt be a good idea. This one is just very simple.
Makefile diff | blob | history
merge-base.c [new file with mode: 0644] blob
The core git plumbing