| author | Junio C Hamano <junkio@cox.net> | |
| Wed, 11 Jan 2006 22:20:09 +0000 (14:20 -0800) | ||
| committer | Junio C Hamano <junkio@cox.net> | |
| Wed, 11 Jan 2006 22:47:20 +0000 (14:47 -0800) | ||
| commit | 2c817df25d54b557d6cac0800cacfd0a255cd56d | |
| tree | 0217463c24b8d982aea3d83a165c1875e988c495 | tree | snapshot |
| parent | a94d9948da539fdafc26c74afb335b2fe9f8f21d | commit | diff |
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>
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>
| name-rev.c | diff | blob | history | |
| t/t6010-merge-base.sh | diff | blob | history |