{"thread":{"id":"42913","subject":"[ANN] Pro Git Reedited 2nd Edition","startedAt":"2016-07-24T04:08:00Z","lastAt":"2016-08-13T00:30:30Z","messageCount":13,"participants":["Jon Forrest","Jakub Narębski","Johannes Schindelin","Manlio Perillo","Sitaram Chamarty"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"292045","messageId":"nn1euf$h6q$1@ger.gmane.org","threadId":"42913","inReplyTo":null,"subject":"[ANN] Pro Git Reedited 2nd Edition","fromName":"Jon Forrest","fromEmail":"nobozo@gmail.com","sentAt":"2016-07-24T04:07:41Z","receivedAt":"2016-07-24T04:08:00Z","isPatch":false,"sender":{"key":"nobozo@gmail.com","avatar":"https://gravatar.com/avatar/37c6a7b57f29b3f35c6a9016537907c52f15bbf98575617dc046bcec6bf06372?d=mp&s=160"},"body":"This an announcement of Pro Git Reedited 2nd Edition, which is\na substantial edit of Chacon and Straub's Pro Git 2nd Edition.\nI spent a lot of time tightening it up and maybe clearing\nup some explanations.\n\nThe pdf is downloadable at:\nhttps://drive.google.com/open?id=0B-Llso12P94-Ujg5Z1dhWUhhMm8\n\nThe complete self-contained HTML is at:\nhttps://drive.google.com/file/d/0B-Llso12P94-U3g1aDBRWjk1Sk0\n\nThe sources for this book are at:\nhttps://github.com/nobozo/progit2\n\nI welcome comments.\n\nJon Forrest\n\n"},{"id":"292051","messageId":"579483B7.4090508@gmail.com","threadId":"42913","inReplyTo":"nn1euf$h6q$1@ger.gmane.org","subject":"Re: [ANN] Pro Git Reedited 2nd Edition","fromName":"Jakub Narębski","fromEmail":"jnareb@gmail.com","sentAt":"2016-07-24T09:00:39Z","receivedAt":"2016-07-24T09:00:57Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"W dniu 2016-07-24 o 06:07, Jon Forrest pisze:\n\n> This an announcement of Pro Git Reedited 2nd Edition, which is\n> a substantial edit of Chacon and Straub's Pro Git 2nd Edition.\n> I spent a lot of time tightening it up and maybe clearing\n> up some explanations.\n[...]\n\n> The sources for this book are at:\n> https://github.com/nobozo/progit2\n\nI have not checked the book itself; it would be nice if it were\nhosted somewhere, even if using GitHub Pages (per-project or\nper-user).\n\nCould you change the description of the repository, and perhaps\nadjust the README so that it says that it is Pro Git Reedited?\nHave you tried submitting changes upstream?\n\nBest,\n-- \nJakub Narębski\nauthor of \"Mastering Git\"\n\n"},{"id":"292062","messageId":"CANQwDwcy_AXTmG02ynNanNvoNVnK+t3uxf5r1J5tHn1hxaZ9kg@mail.gmail.com","threadId":"42913","inReplyTo":"6f7eea6b-2446-5740-cbec-141d71a33ea1@gmail.com","subject":"Re: [ANN] Pro Git Reedited 2nd Edition","fromName":"Jakub Narębski","fromEmail":"jnareb@gmail.com","sentAt":"2016-07-24T17:19:21Z","receivedAt":"2016-07-24T17:20:08Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Re-added git mailing list\n\nOn 24 July 2016 at 17:57, Jon Forrest <jonf@captricity.com> wrote:\n> On 7/24/2016 2:00 AM, Jakub Narębski wrote:\n>\n>> I have not checked the book itself; it would be nice if it were\n>> hosted somewhere, even if using GitHub Pages (per-project or\n>> per-user).\n>\n> Do you mean in some format other than pdf and html?\n> What's wrong with sharing on Google drive?\n\nAs far as I can see you cannot view it online (without downloading).\n\n>> Could you change the description of the repository, and perhaps\n>> adjust the README so that it says that it is Pro Git Reedited?\n>\n> Good idea. I'll do that.\n\nGood.\n\n>> Have you tried submitting changes upstream?\n>\n>\n> Yes, but they're not interested because most of my\n> changes are very subjective. I have submitted a couple\n> of obvious minor errors, which do appear in the upstream\n> version.\n\nAh. Could you tell me the summary of those changes?\n\n-- \nJakub Narebski\n"},{"id":"292063","messageId":"d7918e4a-c4c7-c85f-1aba-3cb9a59e6eba@gmail.com","threadId":"42913","inReplyTo":"CANQwDwcy_AXTmG02ynNanNvoNVnK+t3uxf5r1J5tHn1hxaZ9kg@mail.gmail.com","subject":"Re: [ANN] Pro Git Reedited 2nd Edition","fromName":"Jon Forrest","fromEmail":"nobozo@gmail.com","sentAt":"2016-07-24T17:34:54Z","receivedAt":"2016-07-24T17:35:11Z","isPatch":false,"sender":{"key":"nobozo@gmail.com","avatar":"https://gravatar.com/avatar/37c6a7b57f29b3f35c6a9016537907c52f15bbf98575617dc046bcec6bf06372?d=mp&s=160"},"body":"\nOn 7/24/2016 10:19 AM, Jakub Narębski wrote:\n\n> As far as I can see you cannot view it online (without downloading).\n\nTrue. I changed the way the HTML file is generated so that it\ncontains all the images downloading it is as good as viewing\nit online. I'm not current with the thinking about the merits\nof online viewing vs. downloading. Is one more accepted than the other?\n\nAlso, I realized one potentially major disadvantage of sharing in\nGoogle Drive. This is that the URL will change each time I update\nthe book. Apparently Google is taking away the ability to create\na static link at the end of August 2016.\n\nIf this book turns out to be popular enough that I have to change it\nthen I'll have to revisit how to share it. Github Pages looks interesting\nbut it isn't clear to me how to put this book there since it's written\nin Ascidoc.\n\n> Ah. Could you tell me the summary of those changes?\n\nThere are too many to summarize. Some are of the type that the proofreader\nshould have caught, and others are my attempt to clarify things. Since I\ndon't claim to be a Git expert it remains to be seen how successful I am.\n\nJon\n\n"},{"id":"292065","messageId":"5795087C.4010503@gmail.com","threadId":"42913","inReplyTo":"d7918e4a-c4c7-c85f-1aba-3cb9a59e6eba@gmail.com","subject":"Re: [ANN] Pro Git Reedited 2nd Edition","fromName":"Jakub Narębski","fromEmail":"jnareb@gmail.com","sentAt":"2016-07-24T18:27:08Z","receivedAt":"2016-07-24T18:27:27Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"W dniu 2016-07-24 o 19:34, Jon Forrest pisze:\n> On 7/24/2016 10:19 AM, Jakub Narębski wrote:\n> \n>> As far as I can see you cannot view it online (without downloading).\n> \n> True. I changed the way the HTML file is generated so that it\n> contains all the images downloading it is as good as viewing\n> it online. I'm not current with the thinking about the merits\n> of online viewing vs. downloading. Is one more accepted than the other?\n\nIn my opinion being able to view it online has its advantages.\nEven casual reader can check it, and point errors or offer suggestions\nfor improvements.\n\n> Also, I realized one potentially major disadvantage of sharing in\n> Google Drive. This is that the URL will change each time I update\n> the book. Apparently Google is taking away the ability to create\n> a static link at the end of August 2016.\n\nI think you can share a folder instead, and this would be stable.\nAlternatively, when updating the book you could update the link\nin the GitHub repository description and/or the README for the\nfork.\n\n> If this book turns out to be popular enough that I have to change it\n> then I'll have to revisit how to share it. Github Pages looks interesting\n> but it isn't clear to me how to put this book there since it's written\n> in AsciiDoc.\n\nWell, https://git.github.io/htmldocs/git.html is on GitHub Pages\n(for a project, that is in https://github.com/git/git.github.io repo\nthat is also used for Git Rev News), and it obviously uses AsciiDoc.\n\nYou can use Jekyll, or you can just upload HTML, as described\nin https://help.github.com/articles/creating-project-pages-manually/\n(this one is for per-repo GitHub Pages, i.e. using orphan branch\ngh-pages, not a special named repository like e.g. git.github.io).\nAfter each change / release you would need to rebuild HTML version\nand upload to GitHub pages. This can be automated with hooks.\n\nBTW. I thought that Pro Git used Markdown, not AsciiDoc?\n \n>> Ah. Could you tell me the summary of those changes?\n> \n> There are too many to summarize. Some are of the type that the proofreader\n> should have caught, and others are my attempt to clarify things. Since I\n> don't claim to be a Git expert it remains to be seen how successful I am.\n\nAll right. One issue I have after browsing through changes is that\ndescription of changes and their granularity is severely lacking.\n\"A few more very minor changes.\", \"More piddly changes.\", \"should have\nincluded this in last commit\" are not good commit messages.\n\nIf I find time to comment on changes, I would do that on GitHub,\ncommenting / adding notes on changes there (like the one I posted\nas demo: \n  https://github.com/nobozo/progit2/commit/43ae203c2ccf1a017153de1b41a8c47eb166dba1#commitcomment-18372006\n\nBest,\n-- \nJakub Narebski\n\nauthor of \"Mastering Git\"\nhttps://www.packtpub.com/application-development/mastering-git\nhttp://shop.oreilly.com/product/9781783553754.do\nhttps://www.amazon.com/Mastering-Git-Jakub-Narebski/dp/1783553758\n \n\n"},{"id":"292067","messageId":"89e0a631-6396-e56e-0c1d-37acdbf8eda4@gmail.com","threadId":"42913","inReplyTo":"5795087C.4010503@gmail.com","subject":"Re: [ANN] Pro Git Reedited 2nd Edition","fromName":"Jon Forrest","fromEmail":"nobozo@gmail.com","sentAt":"2016-07-24T18:41:24Z","receivedAt":"2016-07-24T18:41:32Z","isPatch":false,"sender":{"key":"nobozo@gmail.com","avatar":"https://gravatar.com/avatar/37c6a7b57f29b3f35c6a9016537907c52f15bbf98575617dc046bcec6bf06372?d=mp&s=160"},"body":"\n\nOn 7/24/2016 11:27 AM, Jakub Narębski wrote:\n\n> In my opinion being able to view it online has its advantages.\n> Even casual reader can check it, and point errors or offer suggestions\n> for improvements.\n\nAbsolutely. Now that I've finished the editing I'll look\ninto that.\n\n> I think you can share a folder instead, and this would be stable.\n> Alternatively, when updating the book you could update the link\n> in the GitHub repository description and/or the README for the\n> fork.\n\nI'll check your folder idea. If that's correct then that would\nbe an excellent way to do it. I had already thought of updating\nthe README but I'm not sure if this would be sufficient.\n\n> Well, https://git.github.io/htmldocs/git.html is on GitHub Pages\n> (for a project, that is in https://github.com/git/git.github.io repo\n> that is also used for Git Rev News), and it obviously uses AsciiDoc.\n\nI'll check that.\n\n> You can use Jekyll, or you can just upload HTML, as described\n> in https://help.github.com/articles/creating-project-pages-manually/\n> (this one is for per-repo GitHub Pages, i.e. using orphan branch\n> gh-pages, not a special named repository like e.g. git.github.io).\n> After each change / release you would need to rebuild HTML version\n> and upload to GitHub pages. This can be automated with hooks.\n\nI'll also look into that.\n\nThese are all great suggestions, which I appreciate. I didn't\ndo any of this for the 1st edition, which, in retrospect,\nwas probably a mistake.\n\n> BTW. I thought that Pro Git used Markdown, not AsciiDoc?\n\nNope. Asciidoc. See\nhttps://medium.com/@chacon/living-the-future-of-technical-writing-2f368bd0a272#.fdhsp0zgj\n\n> All right. One issue I have after browsing through changes is that\n> description of changes and their granularity is severely lacking.\n> \"A few more very minor changes.\", \"More piddly changes.\", \"should have\n> included this in last commit\" are not good commit messages.\n\nYou're absolutely right. I probably should have squashed those commits.\nThose comments aren't really intended for public consumption.\nSince I made many changes per commit, I really couldn't give an\ninstructive commit message.\n\nNow that this edition is done, I plan on following good commit\npractices in the future.\n\n> If I find time to comment on changes, I would do that on GitHub,\n> commenting / adding notes on changes there (like the one I posted\n> as demo:\n>   https://github.com/nobozo/progit2/commit/43ae203c2ccf1a017153de1b41a8c47eb166dba1#commitcomment-18372006\n\nThat would be great. I think I'm setup for that now in my GitHub\nrepo for that book.\n\nJon\n\n"},{"id":"292073","messageId":"49f49b92-bc40-e975-10e9-fccc8a3ae25c@gmail.com","threadId":"42913","inReplyTo":"5795087C.4010503@gmail.com","subject":"Re: [ANN] Pro Git Reedited 2nd Edition","fromName":"Jon Forrest","fromEmail":"nobozo@gmail.com","sentAt":"2016-07-24T20:03:56Z","receivedAt":"2016-07-24T20:04:02Z","isPatch":false,"sender":{"key":"nobozo@gmail.com","avatar":"https://gravatar.com/avatar/37c6a7b57f29b3f35c6a9016537907c52f15bbf98575617dc046bcec6bf06372?d=mp&s=160"},"body":">> Also, I realized one potentially major disadvantage of sharing in\n>> Google Drive. This is that the URL will change each time I update\n>> the book. Apparently Google is taking away the ability to create\n>> a static link at the end of August 2016.\n>\n> I think you can share a folder instead, and this would be stable.\n> Alternatively, when updating the book you could update the link\n> in the GitHub repository description and/or the README for the\n> fork.\n\nBy the way, I might have just figured out a good way of handling\nstatic links with Google Drive.\n\nApparently, when I created the pdf version of Pro Git Reedited\n2nd Edition (which I did on a Dropbox folder) I didn't wait\nlong enough for the creation process to complete (I think\nthat was the problem but I'm not 100% sure). Anyway, as\na result, the pdf version didn't have any images in it.\n\nAfter fooling around for a while, I was able to create a\npdf that did contain the images but I was worried that uploading\nit to Google Drive would change the URL, as we had discussed.\n\nHowever, the \"Manage Versions ...\" option on Google Drive let\nme upload a new version of the file *without* changing the\nshare URL! Assuming I wasn't hallucinating, this will be a\ngreat way to update both the pdf and the HTML versions as\nthey change in the future.\n\nJon\n\n"},{"id":"292081","messageId":"alpine.DEB.2.20.1607250900260.14111@virtualbox","threadId":"42913","inReplyTo":"89e0a631-6396-e56e-0c1d-37acdbf8eda4@gmail.com","subject":"Re: [ANN] Pro Git Reedited 2nd Edition","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2016-07-25T07:04:49Z","receivedAt":"2016-07-25T07:06:14Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Jon,\n\nOn Sun, 24 Jul 2016, Jon Forrest wrote:\n\n> On 7/24/2016 11:27 AM, Jakub Narębski wrote:\n> \n> > All right. One issue I have after browsing through changes is that\n> > description of changes and their granularity is severely lacking.  \"A\n> > few more very minor changes.\", \"More piddly changes.\", \"should have\n> > included this in last commit\" are not good commit messages.\n> \n> You're absolutely right. I probably should have squashed those commits.\n> Those comments aren't really intended for public consumption.\n> Since I made many changes per commit, I really couldn't give an\n> instructive commit message.\n> \n> Now that this edition is done, I plan on following good commit\n> practices in the future.\n\nFor the record: I found it a good practice to clean up my commits (read:\nreword commit messages, split/join commits) *even after* pushing them to a\npublic repository.\n\nInteractive rebase to the rescue.\n\nThat practice is not solely for others' benefit, by the way.\n\nYou will most likely find that it not only structures your work better,\nyou will also find that it turns up things that were forgotten and still\nneed to be addressed.\n\nCiao,\nJohannes"},{"id":"292185","messageId":"CAAToxAFuyzjf1-W4J5v1hpeyn_N4T086nb--+i0dS4QmarW5dQ@mail.gmail.com","threadId":"42913","inReplyTo":"nn1euf$h6q$1@ger.gmane.org","subject":"Re: [ANN] Pro Git Reedited 2nd Edition","fromName":"Manlio Perillo","fromEmail":"manlio.perillo@gmail.com","sentAt":"2016-07-26T09:15:52Z","receivedAt":"2016-07-26T09:15:59Z","isPatch":false,"sender":{"key":"manlio.perillo@gmail.com","avatar":"https://avatars.githubusercontent.com/u/6217088?v=4"},"body":"On Sun, Jul 24, 2016 at 6:07 AM, Jon Forrest <nobozo@gmail.com> wrote:\n> This an announcement of Pro Git Reedited 2nd Edition, which is\n> a substantial edit of Chacon and Straub's Pro Git 2nd Edition.\n> I spent a lot of time tightening it up and maybe clearing\n> up some explanations.\n>\n> The pdf is downloadable at:\n> https://drive.google.com/open?id=0B-Llso12P94-Ujg5Z1dhWUhhMm8\n>\n\nThanks for your work.\n\nI have noted a problem when reading the PDF with Chromium: the\nanchors/links do not work.\n\nI don't know if this is an issue with the conversion to PDF or an\nissue with Chromium.\n\n\nManlio\n"},{"id":"292210","messageId":"50fcb173-8edd-26cd-4828-977d5f1e6b9d@gmail.com","threadId":"42913","inReplyTo":"CAAToxAFuyzjf1-W4J5v1hpeyn_N4T086nb--+i0dS4QmarW5dQ@mail.gmail.com","subject":"Re: [ANN] Pro Git Reedited 2nd Edition","fromName":"Jon Forrest","fromEmail":"nobozo@gmail.com","sentAt":"2016-07-26T14:22:06Z","receivedAt":"2016-07-26T14:22:17Z","isPatch":false,"sender":{"key":"nobozo@gmail.com","avatar":"https://gravatar.com/avatar/37c6a7b57f29b3f35c6a9016537907c52f15bbf98575617dc046bcec6bf06372?d=mp&s=160"},"body":"\n\nOn 7/26/2016 2:15 AM, Manlio Perillo wrote:\n\n> I have noted a problem when reading the PDF with Chromium: the\n> anchors/links do not work.\n\nI see what you mean. I was able to replicate the problem with Acrobat\nReader on Windows 10. This seems to happen only with internal links - links\nto external URLs work fine.\n\n> I don't know if this is an issue with the conversion to PDF or an\n> issue with Chromium.\n\nIt's not Chromium.\n\nThis is going to be tricky to fix. I'm just using the tool chain\nthat Scott and Ben set up. I've found other issues too that will\nbe hard to resolve.\n\nThanks for the report. I guess for now the best thing to do is\nto use the HTML version.\n\nJon\n\n"},{"id":"298836","messageId":"d2ef9717-beb2-2661-d0b0-4e33f82511ae@gmail.com","threadId":"42913","inReplyTo":"nn1euf$h6q$1@ger.gmane.org","subject":"Re: [ANN] Pro Git Reedited 2nd Edition","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2016-08-12T13:11:03Z","receivedAt":"2016-08-12T13:11:40Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On 07/24/2016 09:37 AM, Jon Forrest wrote:\n> This an announcement of Pro Git Reedited 2nd Edition, which is\n> a substantial edit of Chacon and Straub's Pro Git 2nd Edition.\n> I spent a lot of time tightening it up and maybe clearing\n> up some explanations.\n> \n> The pdf is downloadable at:\n> https://drive.google.com/open?id=0B-Llso12P94-Ujg5Z1dhWUhhMm8\n> \n> The complete self-contained HTML is at:\n> https://drive.google.com/file/d/0B-Llso12P94-U3g1aDBRWjk1Sk0\n> \n> The sources for this book are at:\n> https://github.com/nobozo/progit2\n> \n> I welcome comments.\n\nHi\n\nWhile I'm kinda happy to see the chapter on gitolite gone (for reasons\nof difficulty in keeping it current at that time), I humbly suggest that\na brief mention of gitolite somewhere in the chapter on \"git on the\nserver\" would be useful.\n\nAt present gitolite is -- AFAIK -- the only \"pure server side\", \"no GUI\"\nsolution for access control, and has some interesting features that more\n\"GUI\" solutions may not.  It is also (again, AFAIK) used by kernel.org,\nFedora, Gentoo, and several other open source projects as well as many\nenterprises.\n\nIf you're ok with adding that, I'd be happy to supply some text for your\nconsideration.\n\nregards\nsitaram\n"},{"id":"298838","messageId":"be1b1fcd-48d7-facd-f45c-0c52e6c12e88@gmail.com","threadId":"42913","inReplyTo":"d2ef9717-beb2-2661-d0b0-4e33f82511ae@gmail.com","subject":"Re: [ANN] Pro Git Reedited 2nd Edition","fromName":"Jon Forrest","fromEmail":"nobozo@gmail.com","sentAt":"2016-08-12T14:37:15Z","receivedAt":"2016-08-12T14:37:24Z","isPatch":false,"sender":{"key":"nobozo@gmail.com","avatar":"https://gravatar.com/avatar/37c6a7b57f29b3f35c6a9016537907c52f15bbf98575617dc046bcec6bf06372?d=mp&s=160"},"body":"\n\nOn 8/12/16 6:11 AM, Sitaram Chamarty wrote:\n\n> At present gitolite is -- AFAIK -- the only \"pure server side\", \"no GUI\"\n> solution for access control, and has some interesting features that more\n> \"GUI\" solutions may not.  It is also (again, AFAIK) used by kernel.org,\n> Fedora, Gentoo, and several other open source projects as well as many\n> enterprises.\n>\n> If you're ok with adding that, I'd be happy to supply some text for your\n> consideration.\n\nI appreciate your offer and I don't disagree with what you're\nsuggesting, but my goal, for now at least, is to keep the same coverage \nas upstream.\n\nIf they add something about Gitolite to their next edition, then\nI will also.\n\nCordially,\nJon Forrest\n\n"},{"id":"298945","messageId":"0e542a52-16ed-8967-fe1d-bfb5a728518c@gmail.com","threadId":"42913","inReplyTo":"be1b1fcd-48d7-facd-f45c-0c52e6c12e88@gmail.com","subject":"Re: [ANN] Pro Git Reedited 2nd Edition","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2016-08-13T00:30:21Z","receivedAt":"2016-08-13T00:30:30Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"On 08/12/2016 08:07 PM, Jon Forrest wrote:\n> \n> \n> On 8/12/16 6:11 AM, Sitaram Chamarty wrote:\n> \n>> At present gitolite is -- AFAIK -- the only \"pure server side\", \"no GUI\"\n>> solution for access control, and has some interesting features that more\n>> \"GUI\" solutions may not.  It is also (again, AFAIK) used by kernel.org,\n>> Fedora, Gentoo, and several other open source projects as well as many\n>> enterprises.\n>>\n>> If you're ok with adding that, I'd be happy to supply some text for your\n>> consideration.\n> \n> I appreciate your offer and I don't disagree with what you're\n> suggesting, but my goal, for now at least, is to keep the same coverage as upstream.\n> \n> If they add something about Gitolite to their next edition, then\n> I will also.\n\nOh ok; I must have misunderstood what \"2nd edition\" means, or did not read your\noriginal email carefully enough.\n\n"}]}