From: "Scott Chacon" <schacon@gmail.com>
To: "Wincent Colaiuta" <win@wincent.com>
Cc: "git list" <git@vger.kernel.org>
Subject: Re: markdown 2 man, was Re: Git Community Book
Date: Wed, 30 Jul 2008 17:13:43 -0700 [thread overview]
Message-ID: <d411cc4a0807301713o6b1fd2e8lde0636352f8f1c5b@mail.gmail.com> (raw)
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:
> 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
>> 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
>
>
next prev parent reply other threads:[~2008-07-31 0:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 16:20 Git Community Book Scott Chacon
2008-07-29 16:28 ` Miklos Vajna
2008-07-29 17:09 ` Petr Baudis
2008-07-29 18:30 ` Scott Chacon
2008-07-29 18:42 ` Junio C Hamano
2008-07-29 19:00 ` Julian Phillips
2008-07-29 19:09 ` Junio C Hamano
2008-07-30 13:27 ` markdown 2 man, was " Johannes Schindelin
2008-07-30 19:32 ` Junio C Hamano
2008-07-30 23:48 ` Wincent Colaiuta
2008-07-31 0:13 ` Scott Chacon [this message]
2008-07-31 0:30 ` Junio C Hamano
2008-07-31 11:24 ` Abdelrazak Younes
2008-07-31 13:01 ` Stephan Beyer
2008-07-31 14:13 ` Abdelrazak Younes
2008-07-31 14:33 ` Abdelrazak Younes
2008-07-31 15:09 ` Miklos Vajna
2008-07-31 15:29 ` Abdelrazak Younes
2008-07-31 19:00 ` Miklos Vajna
2008-08-01 0:45 ` Junio C Hamano
2008-08-01 7:11 ` Abdelrazak Younes
2008-08-01 9:46 ` Thomas Rast
2008-08-01 10:19 ` Abdelrazak Younes
2008-07-31 20:57 ` Jan Krüger
2008-08-01 7:50 ` Abdelrazak Younes
2008-08-01 10:45 ` Dmitry Potapov
2008-08-01 11:06 ` Abdelrazak Younes
2008-07-29 19:34 ` Scott Chacon
2008-07-29 19:57 ` Junio C Hamano
2008-07-30 21:39 ` J. Bruce Fields
2008-07-29 17:43 ` Junio C Hamano
2008-07-29 18:25 ` Junio C Hamano
2008-07-29 19:29 ` Scott Chacon
2008-07-29 19:24 ` Scott Chacon
2008-07-29 22:34 ` Daniel Barkalow
2008-07-29 22:47 ` Junio C Hamano
2008-07-30 13:20 ` Bart Trojanowski
2008-07-30 18:27 ` Junio C Hamano
2008-07-30 13:31 ` Bart Trojanowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d411cc4a0807301713o6b1fd2e8lde0636352f8f1c5b@mail.gmail.com \
--to=schacon@gmail.com \
--cc=git@vger.kernel.org \
--cc=win@wincent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).