From: Scott Chacon <schacon@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: Pro Git Book
Date: Wed, 29 Jul 2009 08:38:49 -0700 [thread overview]
Message-ID: <d411cc4a0907290838r228aaa18yb748fd97d4be01d2@mail.gmail.com> (raw)
In-Reply-To: <m34osv3kah.fsf@localhost.localdomain>
Hey,
On Wed, Jul 29, 2009 at 2:34 AM, Jakub Narebski<jnareb@gmail.com> wrote:
>
> Wonderfull news! Thanks a lot for publishing it under Creative
> Commons (CC-BY-NC-SA 3.0) license for all to see (and improve).
>
> I'll send a few comments later (BTW. would you prefer to have it here,
> or private?).
You can either email them to me or fork the markdown source
(http://github.com/progit/progit) and send me a pull request or patch.
Or just push fixes to your fork - I've been checking them pretty
often since people are starting to translate it on GitHub.
>
> One comment about on-line version: it might be better to have one
> chapter and not one (sub)section per HTML page. There are some
> sections that are not enough to even fill one single page.
>
I agree that some of the pages are small, but I like being able to
point someone at a section for help with something - a whole chapter I
think would be overwhelming. Eventually I'd like to possibly add a
commenting system inline and having one per section would be a lot
more manageable.
Thanks,
Scott
next prev parent reply other threads:[~2009-07-29 16:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 17:56 Pro Git Book Scott Chacon
2009-07-27 21:16 ` Tim Visher
2009-07-28 8:56 ` David Aguilar
2009-07-28 16:14 ` Scott Chacon
2009-07-29 9:34 ` Jakub Narebski
2009-07-29 15:38 ` Scott Chacon [this message]
2009-07-29 18:30 ` Sverre Rabbelier
2009-07-30 15:51 ` Luciano Rocha
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=d411cc4a0907290838r228aaa18yb748fd97d4be01d2@mail.gmail.com \
--to=schacon@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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).