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

Re: What's in git.git (Sep 2008, #02; Wed, 10)

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 11, 2008, 22:02 UTC
Message-ID
<7v8wtys5n8.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<48C8E061.5030904@fastmail.fm>
Michael J Gruber <michaeljgruber+gmane@fastmail.fm> writes:
> I think the cleanest approach would consist in introducing another
> linkgit macro (for everything linkgit:git-) which ouputs dashed resp.
> dashless forms for docbook (i.e. man) resp. html targets. I'll cook up a
> POC if noone keeps me from doing so ;)

I personally think the links are Ok to be left as they are in git-foo form but if there is a good way to persuade manual viewers to display "git foo" and still follow "man git-foo", that would be great.

Names of the programs in "git-foo" form in the plain text, unless they are the server side programs, should be updated to say "git foo" (cf. http://thread.gmane.org/gmane.comp.version-control.git/95436/focus=95443)

Previous: Michael J Gruber
Message 3 of 3 in “What's in git.git (Sep 2008, #02; Wed, 10)”
  1. Junio C HamanoSep 11, 2008
  2. Michael J GruberSep 11, 2008
  3. Junio C HamanoSep 11, 2008

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.