git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Jakub Narębski" <jnareb@gmail.com>
To: Jon Forrest <nobozo@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [ANN] Pro Git Reedited 2nd Edition
Date: Sun, 24 Jul 2016 20:27:08 +0200	[thread overview]
Message-ID: <5795087C.4010503@gmail.com> (raw)
In-Reply-To: <d7918e4a-c4c7-c85f-1aba-3cb9a59e6eba@gmail.com>

W dniu 2016-07-24 o 19:34, Jon Forrest pisze:
> On 7/24/2016 10:19 AM, Jakub Narębski wrote:
> 
>> As far as I can see you cannot view it online (without downloading).
> 
> True. I changed the way the HTML file is generated so that it
> contains all the images downloading it is as good as viewing
> it online. I'm not current with the thinking about the merits
> of online viewing vs. downloading. Is one more accepted than the other?

In my opinion being able to view it online has its advantages.
Even casual reader can check it, and point errors or offer suggestions
for improvements.

> Also, I realized one potentially major disadvantage of sharing in
> Google Drive. This is that the URL will change each time I update
> the book. Apparently Google is taking away the ability to create
> a static link at the end of August 2016.

I think you can share a folder instead, and this would be stable.
Alternatively, when updating the book you could update the link
in the GitHub repository description and/or the README for the
fork.

> If this book turns out to be popular enough that I have to change it
> then I'll have to revisit how to share it. Github Pages looks interesting
> but it isn't clear to me how to put this book there since it's written
> in AsciiDoc.

Well, https://git.github.io/htmldocs/git.html is on GitHub Pages
(for a project, that is in https://github.com/git/git.github.io repo
that is also used for Git Rev News), and it obviously uses AsciiDoc.

You can use Jekyll, or you can just upload HTML, as described
in https://help.github.com/articles/creating-project-pages-manually/
(this one is for per-repo GitHub Pages, i.e. using orphan branch
gh-pages, not a special named repository like e.g. git.github.io).
After each change / release you would need to rebuild HTML version
and upload to GitHub pages. This can be automated with hooks.

BTW. I thought that Pro Git used Markdown, not AsciiDoc?
 
>> Ah. Could you tell me the summary of those changes?
> 
> There are too many to summarize. Some are of the type that the proofreader
> should have caught, and others are my attempt to clarify things. Since I
> don't claim to be a Git expert it remains to be seen how successful I am.

All right. One issue I have after browsing through changes is that
description of changes and their granularity is severely lacking.
"A few more very minor changes.", "More piddly changes.", "should have
included this in last commit" are not good commit messages.

If I find time to comment on changes, I would do that on GitHub,
commenting / adding notes on changes there (like the one I posted
as demo: 
  https://github.com/nobozo/progit2/commit/43ae203c2ccf1a017153de1b41a8c47eb166dba1#commitcomment-18372006

Best,
-- 
Jakub Narebski

author of "Mastering Git"
https://www.packtpub.com/application-development/mastering-git
http://shop.oreilly.com/product/9781783553754.do
https://www.amazon.com/Mastering-Git-Jakub-Narebski/dp/1783553758
 


  reply	other threads:[~2016-07-24 18:27 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
2016-07-24 17:34       ` Jon Forrest
2016-07-24 18:27         ` Jakub Narębski [this message]
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=5795087C.4010503@gmail.com \
    --to=jnareb@gmail.com \
    --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).