{"thread":{"id":"42775","subject":"Missing Package in git Installation Instructions (git-scm.com)","startedAt":"2016-07-04T22:13:38Z","lastAt":"2016-07-05T18:08:35Z","messageCount":4,"participants":["Christoph Michelbach","Johannes Schindelin","Jakub Narębski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"290804","messageId":"1467670411.13990.4.camel@gmail.com","threadId":"42775","inReplyTo":null,"subject":"Missing Package in git Installation Instructions (git-scm.com)","fromName":"Christoph Michelbach","fromEmail":"michelbach94@gmail.com","sentAt":"2016-07-04T22:13:31Z","receivedAt":"2016-07-04T22:13:38Z","isPatch":false,"sender":{"key":"michelbach94@gmail.com","avatar":null},"body":"Hi, I noticed that the instructions on https://git-scm.com/book/en/v2/G\netting-Started-Installing-Git don't work without dh-autoreconf\ninstalled on an apt-get system which isn't listed on that site. Can you\nfix that or tell me whom to tell about this? The website doesn't offer\ncontact information. Just tried this on a fresh Ubuntu 16.04\ninstallation.\n\n-- \nWith kind regards\nChristoph Michelbach\n\n"},{"id":"290809","messageId":"alpine.DEB.2.20.1607050807320.8378@virtualbox","threadId":"42775","inReplyTo":"1467670411.13990.4.camel@gmail.com","subject":"Re: Missing Package in git Installation Instructions (git-scm.com)","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2016-07-05T06:10:45Z","receivedAt":"2016-07-05T06:11:03Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Chris,\n\nOn Tue, 5 Jul 2016, Christoph Michelbach wrote:\n\n> Hi, I noticed that the instructions on https://git-scm.com/book/en/v2/G\n> etting-Started-Installing-Git don't work without dh-autoreconf\n> installed on an apt-get system which isn't listed on that site. Can you\n> fix that or tell me whom to tell about this? The website doesn't offer\n> contact information. Just tried this on a fresh Ubuntu 16.04\n> installation.\n\nWhen you follow that link, do you see this text on the left side?\n\n\tThe source of this book is hosted on GitHub.\n\tPatches, suggestions and comments are welcome.\n\nIt links to https://github.com/progit/progit2 and I am sure your bug\nreport would make an excellent contribution to the bug tracker (\"Issues\")\nin that repository.\n\nIt would probably be even better if you cloned said repository, found the\nrespective file via `git grep apt-get`, fixed it, and opened a Pull\nRequest.\n\nCiao,\nJohannes"},{"id":"290842","messageId":"577BB507.1060603@gmail.com","threadId":"42775","inReplyTo":"alpine.DEB.2.20.1607050807320.8378@virtualbox","subject":"Re: Missing Package in git Installation Instructions (git-scm.com)","fromName":"Jakub Narębski","fromEmail":"jnareb@gmail.com","sentAt":"2016-07-05T13:24:23Z","receivedAt":"2016-07-05T13:25:10Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"W dniu 2016-07-05 o 08:10, Johannes Schindelin pisze:\n> Hi Chris,\n> \n> On Tue, 5 Jul 2016, Christoph Michelbach wrote:\n> \n>> Hi, I noticed that the instructions on https://git-scm.com/book/en/v2/G\n>> etting-Started-Installing-Git don't work without dh-autoreconf\n>> installed on an apt-get system which isn't listed on that site. Can you\n>> fix that or tell me whom to tell about this? The website doesn't offer\n>> contact information. Just tried this on a fresh Ubuntu 16.04\n>> installation.\n> \n> When you follow that link, do you see this text on the left side?\n> \n> \tThe source of this book is hosted on GitHub.\n> \tPatches, suggestions and comments are welcome.\n> \n> It links to https://github.com/progit/progit2 and I am sure your bug\n> report would make an excellent contribution to the bug tracker (\"Issues\")\n> in that repository.\n> \n> It would probably be even better if you cloned said repository, found the\n> respective file via `git grep apt-get`, fixed it, and opened a Pull\n> Request.\n\nOr you can even fix it from a web interface, if you have a GitHub account.\nBehind the scene, GitHub would fork a repository, edit file and create\na commit, then create a pull request.  Very easy for one-off fixes, assuming\nthat you have a GitHub account.\n\n-- \nJakub Narębski\n\n\n"},{"id":"290854","messageId":"1467742106.3047.2.camel@gmail.com","threadId":"42775","inReplyTo":"577BB507.1060603@gmail.com","subject":"Re: Missing Package in git Installation Instructions (git-scm.com)","fromName":"Christoph Michelbach","fromEmail":"michelbach94@gmail.com","sentAt":"2016-07-05T18:08:26Z","receivedAt":"2016-07-05T18:08:35Z","isPatch":false,"sender":{"key":"michelbach94@gmail.com","avatar":null},"body":"Thank you both!\n\nI cloned the repository to fix it yet found it already fixed so assumed\neither of you did that. But according to git blame, that line was last\ntouched 94 days ago by Yue Lin Ho and they made exactly that change. It\nseems to take a long time until they publish it on the website.\n\n-- \nWith kind regards\nChristoph Michelbach\n\nOn Tue, 2016-07-05 at 15:24 +0200, Jakub Narębski wrote:\n> W dniu 2016-07-05 o 08:10, Johannes Schindelin pisze:\n> > \n> > Hi Chris,\n> > \n> > On Tue, 5 Jul 2016, Christoph Michelbach wrote:\n> > \n> > > \n> > > Hi, I noticed that the instructions on https://git-scm.com/book/e\n> > > n/v2/G\n> > > etting-Started-Installing-Git don't work without dh-autoreconf\n> > > installed on an apt-get system which isn't listed on that site.\n> > > Can you\n> > > fix that or tell me whom to tell about this? The website doesn't\n> > > offer\n> > > contact information. Just tried this on a fresh Ubuntu 16.04\n> > > installation.\n> > When you follow that link, do you see this text on the left side?\n> > \n> > \tThe source of this book is hosted on GitHub.\n> > \tPatches, suggestions and comments are welcome.\n> > \n> > It links to https://github.com/progit/progit2 and I am sure your\n> > bug\n> > report would make an excellent contribution to the bug tracker\n> > (\"Issues\")\n> > in that repository.\n> > \n> > It would probably be even better if you cloned said repository,\n> > found the\n> > respective file via `git grep apt-get`, fixed it, and opened a Pull\n> > Request.\n> Or you can even fix it from a web interface, if you have a GitHub\n> account.\n> Behind the scene, GitHub would fork a repository, edit file and\n> create\n> a commit, then create a pull request.  Very easy for one-off fixes,\n> assuming\n> that you have a GitHub account.\n> \n"}]}