From: Jon Forrest <nobozo@gmail.com>
To: Konstantin Khomoutov <kostix@bswap.ru>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"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:24:39 -0800 [thread overview]
Message-ID: <972839aa-c1de-2ec2-b047-44e5df65bd13@gmail.com> (raw)
In-Reply-To: <20181211171553.4mnd66ngqvcxb6me@tigra>
On 12/11/2018 9:15 AM, Konstantin Khomoutov wrote:
> I think an uspoken issue here is that while you're indeed free to "fork"
> this book and maintain your fork, having two books with almost identical
> contents may not be the best option as it simply may be outright
> confusing for those at whom your fork is actually targeted.
The coverage is almost identical, but the content is different.
> That's just my opinion, or — better — feeling I gathered from the
> discussion, but to me these friendly nudges to maybe consider
> reevaluating your work for inclusion into the original's book proper
> look exactly as hints at that having such a fork may not be the best
> of all options.
You might be right, but the reception I got when working on the
first edition led me to make the fork. In retrospect, I probably
should have tried again with the new crew who did the second
edition. As I said, I will try again if there's a third edition.
> Another problem with the fork is its visibility.
> The go-to Git website links to the original work, and I assure you
> novice users do not casually read this list — let alone search through
> its archives for the mentions of an alternative book's version.
I agree, and I don't know what to do about that.
Jon
next prev parent reply other threads:[~2018-12-11 17:24 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
2018-12-11 17:15 ` Konstantin Khomoutov
2018-12-11 17:24 ` Jon Forrest [this message]
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=972839aa-c1de-2ec2-b047-44e5df65bd13@gmail.com \
--to=nobozo@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=kostix@bswap.ru \
--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).