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

Re: [PATCH] Documentation/revisions: Document shorthand

From
Johan Sageryd <j416@1616.se>
Date
Jul 1, 2011, 23:01 UTC
Message-ID
<4E0E51D2.9070407@1616.se>
In-Reply-To
<4E0C2627.9040709@drmicha.warpmail.net>
On 2011-06-30 09.30, Michael J Gruber wrote:
> If rev~ is meant to be documented usage (I thought rev^ to be preferred
> but may be wrong) then we should make the descriptions of rev~<n> and
> rev^<n> more uniform.
Hello Michael,

Yes, I thought about this too, there is indeed room for improvement. However in that case we should also think about uniforming the descriptions of for instance "<refname>@{<n>}", "@{<n>}", "@{-<n>}" in a similar way.

The current descriptions are in themselves quite clear and I didn't feel the need to spend much time rewriting it all. But I do believe that we should strive to document all possible syntax, preferred or not, and that is the reason for me suggesting this patch. The more complete the better, optimising can be done at any time.

Johan
Previous: Michael J Gruber
Message 3 of 3 in “Documentation/revisions: Document shorthand”
  1. Documentation/revisions: Document shorthandJohan Sageryd, Jun 28, 2011
  2. Michael J GruberJun 30, 2011
  3. Johan SagerydJul 1, 2011

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.