git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jon Forrest <nobozo@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Jeff King <peff@peff.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Announcing Pro Git Second Edition Reedited
Date: Tue, 11 Dec 2018 09:00:31 -0800	[thread overview]
Message-ID: <55838db9-4f08-b77e-bc95-5c7dce4024d2@gmail.com> (raw)
In-Reply-To: <CACBZZX6g7TaxNHN=3ApV4wV91ZuVV8eoemMurS=WMt4mG8Q67g@mail.gmail.com>



On 12/11/2018 7:13 AM, Ævar Arnfjörð Bjarmason wrote:

> As someone who's read neither your edit or the original edition, but I
> did read your version of the intro, it would be very helpful to me /
> others if there was some diff between the two so we could make up our
> own mind about which one to read, and to get an idea of what sorts of
> wording changes etc. these are.

That would indeed be nice. The best I can do is to suggest that if
you're satisfied with the regular Pro Git then my version won't
help you. On the other hand, if you find regular Pro Git puzzling,
especially in the early chapters, I suggest giving my version a try.

Since I'm giving away my version, you have nothing to loose except
perhaps a little time. If I'm right, and my version is clearer, then
you could benefit from it.

(You're a git expert so I doubt you need my version).

Cordially,
Jon Forrest


  reply	other threads:[~2018-12-11 17:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-09 18:42 Announcing Pro Git Second Edition Reedited Jon Forrest
2018-12-11 10:50 ` Jeff King
2018-12-11 14:39   ` Jon Forrest
2018-12-11 15:13     ` Ævar Arnfjörð Bjarmason
2018-12-11 17:00       ` Jon Forrest [this message]
2018-12-11 17:15         ` Konstantin Khomoutov
2018-12-11 17:24           ` Jon Forrest
2018-12-12  7:58     ` Robert P. J. Day

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55838db9-4f08-b77e-bc95-5c7dce4024d2@gmail.com \
    --to=nobozo@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).