author | Junio C Hamano <gitster@pobox.com> | |
Tue, 28 Aug 2007 07:38:48 +0000 (00:38 -0700) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Tue, 28 Aug 2007 07:38:48 +0000 (00:38 -0700) | ||
commit | 8a1d076e21810f5bc7e9ef10d84f7ca9637b89af | |
tree | 02044913746de08e73295921df2053306eb5236c | tree | snapshot |
parent | 170c04383bca07fb5a32227474dfd58f29258d25 | commit | diff |
"format-patch --root rev" is the way to show everything.
We used to trigger the special case "things not in origin"
semantics only when one and only one positive ref is given, and
no number (e.g. "git format-patch -4 origin") was specified, and
used the general revision range semantics for everything else.
This narrows the special case a bit more, by making:
git format-patch --root this_version
to show everything that leads to the named commit.
More importantly, document the two different semantics better.
The generic revision range semantics came later and bolted on
without being clearly documented.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
We used to trigger the special case "things not in origin"
semantics only when one and only one positive ref is given, and
no number (e.g. "git format-patch -4 origin") was specified, and
used the general revision range semantics for everything else.
This narrows the special case a bit more, by making:
git format-patch --root this_version
to show everything that leads to the named commit.
More importantly, document the two different semantics better.
The generic revision range semantics came later and bolted on
without being clearly documented.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-format-patch.txt | diff | blob | history | |
builtin-log.c | diff | blob | history |