From: Jon Forrest <nobozo@gmail.com>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [ANN] Pro Git Reedited 2nd Edition
Date: Sun, 24 Jul 2016 13:03:56 -0700 [thread overview]
Message-ID: <49f49b92-bc40-e975-10e9-fccc8a3ae25c@gmail.com> (raw)
In-Reply-To: <5795087C.4010503@gmail.com>
>> 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.
By the way, I might have just figured out a good way of handling
static links with Google Drive.
Apparently, when I created the pdf version of Pro Git Reedited
2nd Edition (which I did on a Dropbox folder) I didn't wait
long enough for the creation process to complete (I think
that was the problem but I'm not 100% sure). Anyway, as
a result, the pdf version didn't have any images in it.
After fooling around for a while, I was able to create a
pdf that did contain the images but I was worried that uploading
it to Google Drive would change the URL, as we had discussed.
However, the "Manage Versions ..." option on Google Drive let
me upload a new version of the file *without* changing the
share URL! Assuming I wasn't hallucinating, this will be a
great way to update both the pdf and the HTML versions as
they change in the future.
Jon
next prev parent reply other threads:[~2016-07-24 20:04 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
2016-07-24 18:41 ` Jon Forrest
2016-07-25 7:04 ` Johannes Schindelin
2016-07-24 20:03 ` Jon Forrest [this message]
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=49f49b92-bc40-e975-10e9-fccc8a3ae25c@gmail.com \
--to=nobozo@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@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).