git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [ANN] Pro Git Reedited 2nd Edition

From
Jon Forrest <nobozo@gmail.com>
Date
Jul 24, 2016, 20:03 UTC
Message-ID
<49f49b92-bc40-e975-10e9-fccc8a3ae25c@gmail.com>
In-Reply-To
<5795087C.4010503@gmail.com>
Show 9 quoted lines
>> 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
Previous: Johannes Schindelin
Message 13 of 13 in “[ANN] Pro Git Reedited 2nd Edition”
  1. Jon ForrestJul 24, 2016
  2. Jakub NarębskiJul 24, 2016
  3. Manlio PerilloJul 26, 2016
  4. Jon ForrestJul 26, 2016
  5. Sitaram ChamartyAug 12, 2016
  6. Jon ForrestAug 12, 2016
  7. Sitaram ChamartyAug 13, 2016
  8. Jakub NarębskiJul 24, 2016
  9. Jon ForrestJul 24, 2016
  10. Jakub NarębskiJul 24, 2016
  11. Jon ForrestJul 24, 2016
  12. Johannes SchindelinJul 25, 2016
  13. Jon ForrestJul 24, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.