git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: nobozo@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 16:13:42 +0100	[thread overview]
Message-ID: <CACBZZX6g7TaxNHN=3ApV4wV91ZuVV8eoemMurS=WMt4mG8Q67g@mail.gmail.com> (raw)
In-Reply-To: <a1941151-9453-5830-7175-7c8e27425274@gmail.com>

On Tue, Dec 11, 2018 at 4:02 PM Jon Forrest <nobozo@gmail.com> wrote:
> On 12/11/2018 2:50 AM, Jeff King wrote:
>
> > 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.
>
> Fair question. I had tried doing this for the first edition of Pro Git,
> but the person who was in charge of accepting changes wasn't a
> native speaker of English. As a result I had a hard time
> convincing him that my changes were necessary. Many of my changes
> were very subjective, and not technical, so this was hard to overcome.
> Things might have been different if I were correcting technical errors
> or adding significant sections to the book. But, since I'm not a Git
> expert, that's not what I was attempting to do.
>
> Things have changed for the better for the second edition of Pro Git.
> Its management seems much more willing to accept the kind of changes
> I make, as shown by their reaction to the excellent work by Robert
> Day. Even so, given the amount of changes I've made, it's unlikely
> that my changes would be accepted.
>
> I do track the changes to the second edition of Pro Git and
> incorporate that ones that still apply into my version.
>
> But I hear what you're saying. Maybe if and when the third edition
> of Pro Git comes out I'll try what you suggest.

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.

  reply	other threads:[~2018-12-11 15:13 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 [this message]
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='CACBZZX6g7TaxNHN=3ApV4wV91ZuVV8eoemMurS=WMt4mG8Q67g@mail.gmail.com' \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=nobozo@gmail.com \
    --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).