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

Aw: Re: [PATCH v3 4/4] glossary: improve definitions of refspec and pathspec

From
Thomas Ackermann <th.acker@arcor.de>
Date
Apr 15, 2013, 18:41 UTC
Message-ID
<298825540.997906.1366051297394.JavaMail.ngmail@webmail19.arcor-online.net>
In-Reply-To
<7v8v4ju0e5.fsf@alter.siamese.dyndns.org>
Show 5 quoted lines
> 
> But I do not know if the description of the longhand ":(top)" is
> unnecessary for the user.  Is the equivalence between it and :/
> described anywhere else in our documentation set?
>

The only complete "documentation" for all of this is in setup.c and I must confess that I missed the subtle difference of "magic words" which can be used in the long form and "magic signatures" which are used in the short form. Because currently there is only one "magic *", from a user perspective I would prefer to document only the short form. So I suggest to drop the "long form" paragraph entirely and start the "short form paragraph" with "A pathspec that begins with a colon `:` has special meaning. If the leading colon `:` is followed by zero or more "magic ..."

--- Thomas

Previous: Junio C Hamano
Message 10 of 10 in “Some small fixes to glossary-content.txt”
  1. 0/4 Some small fixes to glossary-content.txtThomas Ackermann, Apr 15, 2013
  2. 1/4 glossary: remove outdated/misleading/irrelevant entriesThomas Ackermann, Apr 15, 2013
  3. Junio C HamanoApr 15, 2013
  4. 2/4 glossary: improve description of SHA-1 related topicsThomas Ackermann, Apr 15, 2013
  5. 3/4 The name of the hash function is "SHA-1", not "SHA1"Thomas Ackermann, Apr 15, 2013
  6. Junio C HamanoApr 15, 2013
  7. Michael HaggertyApr 16, 2013
  8. 4/4 glossary: improve definitions of refspec and pathspecThomas Ackermann, Apr 15, 2013
  9. Junio C HamanoApr 15, 2013
  10. Aw: Re: [PATCH v3 4/4] glossary: improve definitions of refspec and pathspecThomas Ackermann, Apr 15, 2013

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.