git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git pull --no-ff documentation

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 1, 2012, 20:24 UTC
Message-ID
<7vmx06aqk7.fsf@alter.siamese.dyndns.org>
In-Reply-To
<7EAC0E5241D6431599764E90FA821FCF@PhilipOakley>
"Philip Oakley" <philipoakley@iee.org> writes:
Show 10 quoted lines
>> 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.

Previous: Philip Oakley
Message 4 of 4 in “git pull --no-ff documentation”
  1. 乙酸鋰Oct 1, 2012
  2. Junio C HamanoOct 1, 2012
  3. Philip OakleyOct 1, 2012
  4. Junio C HamanoOct 1, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.