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

Re: git pull --no-ff documentation

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:54:54

"Philip Oakley" [off-list ref] writes:
quoted
This actually is not about --no-ff but about --no-tags.  Any option
that "pull" itself does not care about stops the command line parser
and the remainder of the command line is fed to underlying "fetch".
Should this be said within the documentation's synopsis ?

e.g.
git pull [pull_options] [merge_options] [fetch_options [<repository>
[<refspec>…]]
We certainly could do that, but I was hoping somebody would
volunteer to make it easier to the end users so that they do not
have to remember which one is which.

The "perhaps something like this?" patch was a hint to show the
first step in that preferrable direction.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help