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

Re: [PATCH] Reword -M, when in `git log`s documention, to suggest --follow

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 2, 2010, 18:43 UTC
Message-ID
<7v1vi8e49k.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1262412622-sup-7473@utwig>
Alex Vandiver <alex@chmrr.net> writes:
> most common usage model.  It seems to me like the more correct fix
> would be to move the diff options to later in the file (after the
> options that are `git log`-specific), or to remove them entirely, and
> replace them with a pointer to git diff's options.

IIRC, the apporach we took earlier that people hated and resulted in the current "include" approach was to say "It also takes many of options that diff family of commands take". So reordering may work better but dropping and referring would not, I suspect.

Previous: Alex Vandiver
Message 5 of 5 in “Reword -M, when in `git log`s documention, to suggest --follow”
  1. Reword -M, when in `git log`s documention, to suggest --followAlex Vandiver, Dec 21, 2009
  2. Alex VandiverJan 1, 2010
  3. Junio C HamanoJan 1, 2010
  4. Alex VandiverJan 2, 2010
  5. Junio C HamanoJan 2, 2010

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.