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

Re: [PATCH] Make usage documentation for git-blame and git-annotate consistent.

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 26, 2007, 04:40 UTC
Message-ID
<7vwsvisybm.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20070826031951.GB7644@ruiner>
Brian Hetro <whee@smaertness.net> writes:
> Added git-annotate usage in the synopsis.

I'd rather not do this. The git-annotate wrapper is a transitional measure for backward compatibility, and I do not think we should advertise the options that are added in git-blame there, even though the command option parser is lazy and does not turn them off. Ideally disabling non annotate options would be a good thing to have if it were free, but I do not think it is worth it.

Previous: Brian Hetro
Message 2 of 2 in “Make usage documentation for git-blame and git-annotate consistent.”
  1. Make usage documentation for git-blame and git-annotate consistent.Brian Hetro, Aug 26, 2007
  2. Junio C HamanoAug 26, 2007

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.