git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Samuel Lijin <sxlijin@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [bug?] docs in Documentation/technical/ do not seem to be distributed
Date: Wed, 19 Apr 2017 13:03:09 -0500	[thread overview]
Message-ID: <CAJZjrdWey6atV0rQUborVH0mnev5j8q3Qsny1dgr9hj8_Hz5uw@mail.gmail.com> (raw)
In-Reply-To: <20170419170509.GC28740@aiede.svl.corp.google.com>

On Wed, Apr 19, 2017 at 12:05 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Hi,
>
> Samuel Lijin wrote:
>
>> 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.
>
> This sounds like a packaging bug in Arch Linux and Ubuntu.
>
> That said, at least in Ubuntu, I am not able to reproduce it.  Do
> you have the git-doc (or git-all, which depends on git-doc) package
> installed?

That was the answer on the Ubuntu machine. Doesn't apply to Arch,
though, so I guess I'll reach out upstream there. I've also opened
#994 on the git/git-scm.com repo for this.

Out of curiosity, do you know why it's distributed like that?

Thanks,
Sam

  reply	other threads:[~2017-04-19 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19  6:04 [bug?] docs in Documentation/technical/ do not seem to be distributed Samuel Lijin
2017-04-19 17:05 ` Jonathan Nieder
2017-04-19 18:03   ` Samuel Lijin [this message]
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=CAJZjrdWey6atV0rQUborVH0mnev5j8q3Qsny1dgr9hj8_Hz5uw@mail.gmail.com \
    --to=sxlijin@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    /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).