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

Re: Git in a Nutshell guide

From
Matthieu Moy <matthieu.moy@imag.fr>
Date
Nov 19, 2007, 22:59 UTC
Message-ID
<vpqd4u5zvs3.fsf@bauges.imag.fr>
In-Reply-To
<7v7ikdna24.fsf@gitster.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 5 quoted lines
> I think the ref naming syntax is so commonly used and
> fundamental that we could treat it as prerequiste for individual
> manual pages.  Maybe move the section to git(7)?  That would
> certainly be better than having it in git-rev-parse(1), but does
> not reduce the cross referencing complaints.

Well, obviously, something which isn't addressed by my patch is the fact that some of the documentation an average user needs is in the plumbing man pages.

(Gosh, I was going to cite the manpage for git-log and git-rev-parse as an example, but it has already been fixed :-). Good job !)

git-rev-parse(1) is full of terribly usefull information, and that information is definitely not in the place an average user would look at.

I have no ideal solution for that. git(7) is already really long. Perhaps some "topic man pages" would be good. By "topic man page", I mean "man git-something" where "something" isn't a git command, but a crosscutting concept. For example, here, "man git-refspec" to document reference specifiers like HEAD@{42}, master~55, d71c6c8e24a and friends. "man git-i18n" would be another candidate.

Anyway, my patch is definitely a step forward, even if it's just the first, small one ;-).

-- 
Matthieu
Previous: Junio C HamanoNext: Junio C Hamano
Message 38 of 40 in “Git in a Nutshell guide”
  1. Jonas JuseliusNov 19, 2007
  2. Jakub NarebskiNov 19, 2007
  3. Jonas JuseliusNov 19, 2007
  4. David KågedalNov 22, 2007
  5. Jakub NarebskiNov 23, 2007
  6. Brian DowningNov 19, 2007
  7. Brian DowningNov 19, 2007
  8. Nicolas PitreNov 19, 2007
  9. Jakub NarebskiNov 19, 2007
  10. Jonas JuseliusNov 19, 2007
  11. Benoit SigoureNov 19, 2007
  12. Daniel BarkalowNov 19, 2007
  13. Jonas JuseliusNov 20, 2007
  14. Jakub NarebskiNov 20, 2007
  15. Jan HudecNov 21, 2007
  16. Jakub NarebskiNov 21, 2007
  17. jhud7196@artax.karlin.mff.cuni.czNov 22, 2007
  18. Jonas JuseliusNov 22, 2007
  19. Jonathan del StrotherNov 22, 2007
  20. Johannes SchindelinNov 22, 2007
  21. jhud7196@artax.karlin.mff.cuni.czNov 22, 2007
  22. Lars HjemliNov 19, 2007
  23. Jonas JuseliusNov 19, 2007
  24. Benoit SigoureNov 19, 2007
  25. Lars HjemliNov 19, 2007
  26. Benoit SigoureNov 19, 2007
  27. J. Bruce FieldsNov 19, 2007
  28. Matthieu MoyNov 19, 2007
  29. Doc fix for git-reflog: mention @{...} syntax, and <ref> in synopsys.Matthieu Moy, Nov 19, 2007
  30. Junio C HamanoNov 19, 2007
  31. Doc fix for git-reflog: mention @{...} syntax, and <ref> in synopsys.Matthieu Moy, Nov 19, 2007
  32. Matthieu MoyNov 19, 2007
  33. Benoit SigoureNov 19, 2007
  34. Matthieu MoyNov 19, 2007
  35. Benoit SigoureNov 19, 2007
  36. J. Bruce FieldsNov 19, 2007
  37. Junio C HamanoNov 19, 2007
  38. Matthieu MoyNov 19, 2007
  39. Junio C HamanoNov 19, 2007
  40. Matthieu MoyNov 19, 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.