Thread (1 message) 1 message, 1 author, 2016-06-15

Re: [PATCH v17 14/14] tag.c: implement '--merged' and '--no-merged' options

From: Matthieu Moy <hidden>
Date: 2016-06-15 23:06:36

John Keeping [off-list ref] writes:
On Fri, Sep 18, 2015 at 09:10:08AM +0200, Matthieu Moy wrote:
quoted
The `commit` may be omitted and defaults to HEAD if this is the final
argument.
I find that slightly confusing, although that might just be me.  It's
slightly longer, but I would write:

	The `commit` may be omitted if this is the final argument, in
	which case it defaults to `HEAD`.
Probably clearer indeed.
I also had a look at git-branch(1), which has similar `--merged` and
`--no-merged` options and says:

	Only list branches whose tips are reachable from the specified
	commit (HEAD if not specified).  Implies `--list`.
I think this lacks the "may be omitted if this is the final argument",
which is actually the most confusing (see the other thread "git status
-u is mildly astonishing" for an example of similar confusion).

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help