git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Jon Forrest <nobozo@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Announcing Pro Git Second Edition Reedited
Date: Tue, 11 Dec 2018 05:50:07 -0500	[thread overview]
Message-ID: <20181211105007.GD7233@sigill.intra.peff.net> (raw)
In-Reply-To: <pujni2$ulb$1@blaine.gmane.org>

On Sun, Dec 09, 2018 at 10:42:12AM -0800, Jon Forrest wrote:

> Several years ago I released what I called Pro Git Reedited. This was an
> attempt to tighten up the text of the excellent Pro Git book written by
> Scott Chacon. Since then, Scott and Ben Straub released the second
> edition of Pro Git so once again I'm releasing a reedited version of
> what they wrote. I hope you enjoy it.
> 
> The PDF of my version is at
> 
> https://drive.google.com/file/d/18wGebSU0dyYU1L_bfyoDQtZRF1Vo1H3p/view?usp=sharing
> 
> If there's enough interest, I'll try to put up an HTML version of
> the book.

The content at https://git-scm.com/book is pulled regularly from
https://github.com/progit/progit2, which has collected a number of fixes
(as well as translations) since the 2nd edition was released.

Have you considered sending some of your edits there? It sounds like
they may be too large to just dump as a big PR, but it might be possible
to grow together over time.

-Peff

  reply	other threads:[~2018-12-11 10:50 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 [this message]
2018-12-11 14:39   ` Jon Forrest
2018-12-11 15:13     ` Ævar Arnfjörð Bjarmason
2018-12-11 17:00       ` Jon Forrest
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=20181211105007.GD7233@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=nobozo@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.
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).