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

Re: markdown 2 man, was Re: Git Community Book

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 30, 2008, 19:32 UTC
Message-ID
<7vy73j418t.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<alpine.LSU.1.00.0807301514280.3486@wbgn129.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Note also that Markdown cannot create TOCs automatically, AFAICT.  So 
> probably it would be not all that easy to convert the User Manual to that 
> format.

The use of markdown may mean updates to the User Manual won't be merged back to his book without effort and manual porting on his side, and the side porting in the other direction has the same issue as well, but the contents and the way materials are presented will be vastly different in future versions anyway; not being able to side-port new material verbatim may not be an issue. Discussion with Scott seems to suggest that the overall philosophy of his book is "this is a different book targetted for different audiences; its initial text happens to heavily borrow from the existing documents but expected to become vastly improved", in other words, fork-and-never-return.

That's one valid approach. I or you might have taken a different avenue, but after all, it's his book, not mine, not yours, nor git list's book.

As I am not in "graphics and screencast" camp, I may probably not be able to offer much help improving his book, and I suspect some people on this list might feel the same way. But that's is Ok --- we are not dumping the User Manual.

We originally hoped (well, at least I did) that Scott's effort on his book might help us in improving the User Manual as well, but the approach seems to make it unlikely. But that is nothing to hold against him --- he is doing his own thing in a way he feels is the best, and that's perfectly fine. We lost nothing, perhaps except for a chance to cooperate a bit better and to widen the community.

> If at all, I would have preferred a format switch to Wiki syntax so that 
> we can use the same source on the Git wiki as in our Documentation/ 
> directory.
Yeah, that's also true.  I seem to recall markdown was used in ikiwiki?
Previous: Johannes SchindelinNext: Wincent Colaiuta
Message 9 of 39 in “Git Community Book”
  1. Scott ChaconJul 29, 2008
  2. Miklos VajnaJul 29, 2008
  3. Petr BaudisJul 29, 2008
  4. Scott ChaconJul 29, 2008
  5. Junio C HamanoJul 29, 2008
  6. Julian PhillipsJul 29, 2008
  7. Junio C HamanoJul 29, 2008
  8. markdown 2 man, was Re: Git Community BookJohannes Schindelin, Jul 30, 2008
  9. Junio C HamanoJul 30, 2008
  10. Wincent ColaiutaJul 30, 2008
  11. Scott ChaconJul 31, 2008
  12. Junio C HamanoJul 31, 2008
  13. Abdelrazak YounesJul 31, 2008
  14. Stephan BeyerJul 31, 2008
  15. Abdelrazak YounesJul 31, 2008
  16. Abdelrazak YounesJul 31, 2008
  17. Miklos VajnaJul 31, 2008
  18. Abdelrazak YounesJul 31, 2008
  19. Miklos VajnaJul 31, 2008
  20. Junio C HamanoAug 1, 2008
  21. Abdelrazak YounesAug 1, 2008
  22. Thomas RastAug 1, 2008
  23. Abdelrazak YounesAug 1, 2008
  24. Jan KrügerJul 31, 2008
  25. Abdelrazak YounesAug 1, 2008
  26. Dmitry PotapovAug 1, 2008
  27. Abdelrazak YounesAug 1, 2008
  28. Scott ChaconJul 29, 2008
  29. Junio C HamanoJul 29, 2008
  30. J. Bruce FieldsJul 30, 2008
  31. Junio C HamanoJul 29, 2008
  32. Junio C HamanoJul 29, 2008
  33. Scott ChaconJul 29, 2008
  34. Scott ChaconJul 29, 2008
  35. Daniel BarkalowJul 29, 2008
  36. Junio C HamanoJul 29, 2008
  37. Bart TrojanowskiJul 30, 2008
  38. Junio C HamanoJul 30, 2008
  39. Bart TrojanowskiJul 30, 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.