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

Re: Re* manpage for git-pull mentions a non-valid option -m in a comment

From
Torsten Bögershausen <tboegi@web.de>
Date
Jan 14, 2014, 18:51 UTC
Message-ID
<52D5874D.7070102@web.de>
In-Reply-To
<xmqqvbxm4dyq.fsf@gitster.dls.corp.google.com>
On 2014-01-14 19.26, Junio C Hamano wrote:
Show 28 quoted lines
> Ivan Zakharyaschev <imz@altlinux.org> writes:
> 
>> Hello!
>>
>> git-1.8.4.4
>>
>> The manpage for git-pull mentions -m in a comment:
>>
>> --edit, -e, --no-edit
>> Invoke an editor before committing successful mechanical merge to further edit
>> the auto-generated merge message, so that the user can explain and justify the
>> merge. The --no-edit option can be used to accept the auto-generated message
>> (this is generally discouraged). The --edit (or -e) option is still useful if
>> you are giving a draft message with the -m option from the command line and
>> want to edit it in the editor.
>>
>> but it is not accepted actually:
> 
> I do not think "git pull" ever had the "-m <message>" option; what
> you are seeing probably is a fallout from attempting to share the
> documentation pieces between "git pull" and "git merge" too
> agressively without proofreading.
> 
> It seems that there are two issues; here is an untested attempt to
> fix.
> 
> -- >8 --
> Subject: Documentaiotn: exclude irrelevant options from "git pull"
           ^^^^^^^^^^^^^^
(Small nit ??)
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 6 in “BUG: manpage for git-pull mentions a non-valid option -m in a comment”
  1. Ivan ZakharyaschevJan 14, 2014
  2. Re* manpage for git-pull mentions a non-valid option -m in a commentJunio C Hamano, Jan 14, 2014
  3. Torsten BögershausenJan 14, 2014
  4. Junio C HamanoJan 14, 2014
  5. 1/2 Documentation: exclude irrelevant options from "git pull"Junio C Hamano, Jan 14, 2014
  6. 2/2 Documentation: "git pull" does not have the "-m" optionJunio C Hamano, Jan 14, 2014

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.