From: "Jakub Narębski" <jnareb@gmail.com>
To: Jon Forrest <jonf@captricity.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [ANN] Pro Git Reedited 2nd Edition
Date: Sun, 24 Jul 2016 19:19:21 +0200 [thread overview]
Message-ID: <CANQwDwcy_AXTmG02ynNanNvoNVnK+t3uxf5r1J5tHn1hxaZ9kg@mail.gmail.com> (raw)
In-Reply-To: <6f7eea6b-2446-5740-cbec-141d71a33ea1@gmail.com>
Re-added git mailing list
On 24 July 2016 at 17:57, Jon Forrest <jonf@captricity.com> wrote:
> On 7/24/2016 2:00 AM, Jakub Narębski wrote:
>
>> I have not checked the book itself; it would be nice if it were
>> hosted somewhere, even if using GitHub Pages (per-project or
>> per-user).
>
> Do you mean in some format other than pdf and html?
> What's wrong with sharing on Google drive?
As far as I can see you cannot view it online (without downloading).
>> Could you change the description of the repository, and perhaps
>> adjust the README so that it says that it is Pro Git Reedited?
>
> Good idea. I'll do that.
Good.
>> Have you tried submitting changes upstream?
>
>
> Yes, but they're not interested because most of my
> changes are very subjective. I have submitted a couple
> of obvious minor errors, which do appear in the upstream
> version.
Ah. Could you tell me the summary of those changes?
--
Jakub Narebski
next prev parent reply other threads:[~2016-07-24 17:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-24 4:07 [ANN] Pro Git Reedited 2nd Edition Jon Forrest
2016-07-24 9:00 ` Jakub Narębski
[not found] ` <6f7eea6b-2446-5740-cbec-141d71a33ea1@gmail.com>
2016-07-24 17:19 ` Jakub Narębski [this message]
2016-07-24 17:34 ` Jon Forrest
2016-07-24 18:27 ` Jakub Narębski
2016-07-24 18:41 ` Jon Forrest
2016-07-25 7:04 ` Johannes Schindelin
2016-07-24 20:03 ` Jon Forrest
2016-07-26 9:15 ` Manlio Perillo
2016-07-26 14:22 ` Jon Forrest
2016-08-12 13:11 ` Sitaram Chamarty
2016-08-12 14:37 ` Jon Forrest
2016-08-13 0:30 ` Sitaram Chamarty
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=CANQwDwcy_AXTmG02ynNanNvoNVnK+t3uxf5r1J5tHn1hxaZ9kg@mail.gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jonf@captricity.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).