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

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

From
Scott Chacon <schacon@gmail.com>
Date
Jul 31, 2008, 00:13 UTC
Message-ID
<d411cc4a0807301713o6b1fd2e8lde0636352f8f1c5b@mail.gmail.com>
In-Reply-To
<B7697630-DF9C-4EF0-9D63-9E362CEE125B@wincent.com>
On Wed, Jul 30, 2008 at 4:48 PM, Wincent Colaiuta <win@wincent.com> wrote:
Show 11 quoted lines
> El 30/7/2008, a las 21:32, Junio C Hamano escribió:
>
>> 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.
>
> Funnily enough, he chose to title it the "Git Community Book". Hard to match
> Scott's enthusiasm; this is the second major initiative we've seen from him
> in the last few days (the other being git-scm.com itself) which to the
> casual onlooker might look like the "official" Git homepage and
> documentation, but in both cases development occurred behind the scenes and
> the list was only notified after the fact. Better late than never I suppose.

Not sure what else I could have done - I announced that I was starting a documentation project like this about a week ago on this list, then I started the book 3 days ago (http://github.com/schacon/gitscm/commits/book) and announced it here for initial review yesterday. I haven't told very many people about it yet and I haven't linked to it from git-scm.com yet either. It's been open source from the first minute on GitHub, and the link to the source was on the website I posted here.

Same for the git-scm site - I started it on the 23rd and emailed Pasky about it the next day, and the day after that he began submitting patches to me for it and I announced it on this list. Am I missing something here? Do you think I've been working on these secretly for months, or something? If there is a better communication workflow, I would be happy to do so.

I appreciate that you notice my enthusiasm, though. :)
Scott
Show 17 quoted lines
>> 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.
>
> Even though there might not be an automated way to get changes back from the
> fork, if there are clear improvements made then there is at least no legal
> obstacle to incorporating them back in, the only obstacle would be time and
> willingness to do so manually.
>
>>
> Cheers,
> Wincent
>
>
Previous: Wincent ColaiutaNext: Junio C Hamano
Message 11 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.