kernel/git - git - PowerEL Git System

9784 Commits

6 Branches

36 Tags

131 MiB

Tree: 16a4c6176a

Commit Graph

Author	SHA1	Message	Date
A Large Angry SCM	cd6f207a44	Additional merge-base tests (revised) Signed-off-by: A Large Angry SCM <gitzilla@gmail.com>	19 years ago
Junio C Hamano	2c817df25d	name-rev: do not omit leading components of ref name. In a repository with mainto/1.0 (to keep maintaining the 1.0.X series) and fixo/1.0 (to keep fixes that apply to both 1.0.X series and upwards) branches, "git-name-rev mainto/1.0" answered just "1.0" making things ambiguous. Show refnames unambiguously like show-branch does. Signed-off-by: Junio C Hamano <junkio@cox.net>	19 years ago
Junio C Hamano	53de71f88b	Add test case for merge-base. Although it was shown that the "full contamination" was not really full during the list discussion, the series improves things without incurring extra parsing cost, and here is a test to check that. Signed-off-by: Junio C Hamano <junkio@cox.net>	19 years ago

Author

SHA1

Message

Date

A Large Angry SCM

cd6f207a44

Additional merge-base tests (revised)

Signed-off-by: A Large Angry SCM <gitzilla@gmail.com>

19 years ago

Junio C Hamano

2c817df25d

name-rev: do not omit leading components of ref name.

In a repository with mainto/1.0 (to keep maintaining the 1.0.X
series) and fixo/1.0 (to keep fixes that apply to both 1.0.X
series and upwards) branches, "git-name-rev mainto/1.0" answered
just "1.0" making things ambiguous.  Show refnames unambiguously
like show-branch does.

Signed-off-by: Junio C Hamano <junkio@cox.net>

19 years ago

Junio C Hamano

53de71f88b

Add test case for merge-base.

Although it was shown that the "full contamination" was not really full
during the list discussion, the series improves things without incurring
extra parsing cost, and here is a test to check that.

Signed-off-by: Junio C Hamano <junkio@cox.net>

19 years ago

3 Commits (16a4c6176ad096881d0021f1a922fbcc2835f799)