diff options
| author | Junio C Hamano <junkio@cox.net> | 2005-11-21 20:17:22 (GMT) |
|---|---|---|
| committer | Junio C Hamano <junkio@cox.net> | 2005-11-21 20:21:24 (GMT) |
| commit | 88b5a74883f146eac4b15b30e74bbdeb5ab5a63a (patch) | |
| tree | e7d0f36f60800d43a822b957ab5efd309da47130 /diffcore-rename.c | |
| parent | 60abce3c0f41952de7dc1a4abefcb988898b71a4 (diff) | |
| download | git-88b5a74883f146eac4b15b30e74bbdeb5ab5a63a.zip git-88b5a74883f146eac4b15b30e74bbdeb5ab5a63a.tar.gz git-88b5a74883f146eac4b15b30e74bbdeb5ab5a63a.tar.bz2 | |
format-patch: fix two-argument special case, and make it easier to pick single commits
Luben Tuikov noticed that sometimes being able to say
'git-format-patch <commit>' to format the change a single commit
introduces relative to its parent is handy.
This patch does not support that directly, but it makes sense to
interpret a single argument "rev" to mean "rev^1..rev".
With this, the backward compatibility syntaxes still apply:
- "format-patch master" means "format-patch master..HEAD"
- "format-patch origin master" means "format-patch origin..master"
- "format-patch origin.." means "format-patch origin..HEAD"
But "format-patch a b c d e" formats the changes these five
commits introduce relative to their respective parents. Earlier
it rejected these arguments not in "one..two" form.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'diffcore-rename.c')
0 files changed, 0 insertions, 0 deletions