From: Samuel Lijin <sxlijin@gmail.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: [bug?] docs in Documentation/technical/ do not seem to be distributed
Date: Wed, 19 Apr 2017 01:04:39 -0500 [thread overview]
Message-ID: <CAJZjrdWNQFkWwAO_hmHMzVGNNMfynxsvbWufGvRWX8bZD19Epw@mail.gmail.com> (raw)
It's possible this may have nothing to do with the Git project itself
because I have absolutely no idea how this is handled on the packaging
side or, possibly, if this is actually intended.
There are a couple of links floating around in the man pages pointing
to pages in technical/, such as to technical/api-credentials.html in
gitcredentials(7) [1]. On the website and man pages for Arch Linux and
Ubuntu, this link is broken.
On the website, nothing in technical/ seems to be linked to at all.
(If it is, I didn't spend enough time searching.)
On Arch (git v2.12.2), this link points at
/usr/share/doc/git-doc/technical/api-credentials.html; however, this
file does not exist:
$ ls /usr/share/doc/git-doc
git-subtree.html
On Ubuntu 16.04 LTS (git v2.11.0 from the git-core PPA), this link
points at /usr/share/doc/git/html/technical/api-credentials.html;
however, this file does not exist:
$ ls /usr/share/doc/git/
changelog.Debian.gz
changelog.gz
contrib
copyright
NEWS.Debian.gz
README.Debian
README.emacs
README.md
README.source
RelNotes
[1] https://github.com/git/git/blob/v2.12.2/Documentation/gitcredentials.txt#L184
next reply other threads:[~2017-04-19 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 6:04 Samuel Lijin [this message]
2017-04-19 17:05 ` [bug?] docs in Documentation/technical/ do not seem to be distributed Jonathan Nieder
2017-04-19 18:03 ` Samuel Lijin
2017-04-20 0:43 ` brian m. carlson
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=CAJZjrdWNQFkWwAO_hmHMzVGNNMfynxsvbWufGvRWX8bZD19Epw@mail.gmail.com \
--to=sxlijin@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.
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).