diff options
author | Jeff King <peff@peff.net> | 2013-01-31 01:46:11 -0500 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2013-01-31 16:37:24 -0800 |
commit | d040350813986e0f4bb3aeb977077975c1552606 (patch) | |
tree | b678d552c4808396e346d9dae42503499940b906 /t/t5515/fetch.br-config-explicit | |
parent | docs: clarify git-branch --list behavior (diff) | |
download | tgif-d040350813986e0f4bb3aeb977077975c1552606.tar.xz |
branch: let branch filters imply --list
Currently, a branch filter like `--contains`, `--merged`, or
`--no-merged` is ignored when we are not in listing mode.
For example:
git branch --contains=foo bar
will create the branch "bar" from the current HEAD, ignoring
the `--contains` argument entirely. This is not very
helpful. There are two reasonable behaviors for git here:
1. Flag an error; the arguments do not make sense.
2. Implicitly go into `--list` mode
This patch chooses the latter, as it is more convenient, and
there should not be any ambiguity with attempting to create
a branch; using `--contains` and not wanting to list is
nonsensical.
That leaves the case where an explicit modification option
like `-d` is given. We already catch the case where
`--list` is given alongside `-d` and flag an error. With
this patch, we will also catch the use of `--contains` and
other filter options alongside `-d`.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5515/fetch.br-config-explicit')
0 files changed, 0 insertions, 0 deletions