summaryrefslogtreecommitdiff
path: root/git-clone-script
diff options
context:
space:
mode:
authorJon Seymour <jon.seymour@gmail.com>2005-06-30 01:51:34 (GMT)
committerLinus Torvalds <torvalds@ppc970.osdl.org>2005-06-30 03:53:10 (GMT)
commit99c2bc93000dfadc3ac26ddced23e50520cf30d0 (patch)
tree6f7bdf5740f757d49d02a16ea691e6093373e60c /git-clone-script
parentda4b932a0c5b249694216b1580b7bc2ded9e0280 (diff)
downloadgit-99c2bc93000dfadc3ac26ddced23e50520cf30d0.zip
git-99c2bc93000dfadc3ac26ddced23e50520cf30d0.tar.gz
git-99c2bc93000dfadc3ac26ddced23e50520cf30d0.tar.bz2
[PATCH] Fix for git-rev-list --merge-order B ^A (A,B share common base) [rev 2]
This patch makes --merge-order produce the same list as git-rev-list without --merge-order specified. In particular, if the graph looks like this: A | B |/ C | D The both git-rev-list B ^A and git-rev-list --merge-order will produce B. The unit tests have been changed to reflect the fact that the prune points are now formally part of the start list that is used to perform the --merge-order sort. That is: git-rev-list --merge-order A ^D used to produce = A | C It now produces: ^ A | C Signed-off-by: Jon Seymour <jon.seymour@gmail.com> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'git-clone-script')
0 files changed, 0 insertions, 0 deletions