From: "Jakub Narębski" <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: git@vger.kernel.org
Subject: Re: Missing Package in git Installation Instructions (git-scm.com)
Date: Tue, 5 Jul 2016 15:24:23 +0200 [thread overview]
Message-ID: <577BB507.1060603@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1607050807320.8378@virtualbox>
W dniu 2016-07-05 o 08:10, Johannes Schindelin pisze:
> Hi Chris,
>
> On Tue, 5 Jul 2016, Christoph Michelbach wrote:
>
>> Hi, I noticed that the instructions on https://git-scm.com/book/en/v2/G
>> etting-Started-Installing-Git don't work without dh-autoreconf
>> installed on an apt-get system which isn't listed on that site. Can you
>> fix that or tell me whom to tell about this? The website doesn't offer
>> contact information. Just tried this on a fresh Ubuntu 16.04
>> installation.
>
> When you follow that link, do you see this text on the left side?
>
> The source of this book is hosted on GitHub.
> Patches, suggestions and comments are welcome.
>
> It links to https://github.com/progit/progit2 and I am sure your bug
> report would make an excellent contribution to the bug tracker ("Issues")
> in that repository.
>
> It would probably be even better if you cloned said repository, found the
> respective file via `git grep apt-get`, fixed it, and opened a Pull
> Request.
Or you can even fix it from a web interface, if you have a GitHub account.
Behind the scene, GitHub would fork a repository, edit file and create
a commit, then create a pull request. Very easy for one-off fixes, assuming
that you have a GitHub account.
--
Jakub Narębski
next prev parent reply other threads:[~2016-07-05 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 22:13 Missing Package in git Installation Instructions (git-scm.com) Christoph Michelbach
2016-07-05 6:10 ` Johannes Schindelin
2016-07-05 13:24 ` Jakub Narębski [this message]
2016-07-05 18:08 ` Christoph Michelbach
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=577BB507.1060603@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).