From: "Philip Oakley" <philipoakley@iee.org>
To: "Fredrik Gustafsson" <iveqy@iveqy.com>,
"Andrew Johnson" <ajohnson388@gmail.com>,
"Jakub Narębski" <jnareb@gmail.com>
Cc: <git@vger.kernel.org>, "Christian Couder" <christian.couder@gmail.com>
Subject: Re: Why are there multiple ways to get the manual in Git?
Date: Sun, 18 Sep 2016 11:51:41 +0100 [thread overview]
Message-ID: <630656BFF8F84E43A2E4C67138A9A675@PhilipOakley> (raw)
In-Reply-To: 223e818d-6d10-2679-c2d0-150011e74a59@gmail.com
From: "Jakub Narębski" <jnareb@gmail.com>
>W dniu 17.09.2016 o 20:39, Fredrik Gustafsson pisze:
>> On Sat, Sep 17, 2016 at 01:47:52PM -0400, Andrew Johnson wrote:
>
>>> $ git help <verb>
>>> $ git <verb> --help
>>> $ man git-<verb>
>>>
>>> I tested all three to confirm they were equivalent.
>>
>> While I'm not able to answer your question, I can shred a little light
>> about them not being equal. For example using a windows machine
>>
>> $ man git-<verb>
>>
>> does not work and
>>
>> $ git help <verb>
>>
>> opens a webbrowser instead of a man page. Using a unix system I would
>> however assume that
>>
>> $ man git-<verb>
>>
>> would work since it's the standard way of getting help on those systems.
>
> There is also additional difference. There are help pages which are
> not about specific Git command, but about concepts (gitcli, gitrevisions,
> githooks, gitrepository-layout, gitglossary), or about files (gitignore,
> gitattributes, to some extent githooks).
>
> Those are only accessible with `git help <concept>` or, on OS with
> installed 'man', also `man <gitconcept>`.
The `git revisions --help` does work ;-) But like you say, its apparent
"command" name is 'gitrevisions'.
Thus real commands gave a git-command name, while concepts have a gitconcept
name which can then be found via the man command.
--
Philip
next prev parent reply other threads:[~2016-09-18 10:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 17:47 Why are there multiple ways to get the manual in Git? Andrew Johnson
2016-09-17 18:39 ` Fredrik Gustafsson
2016-09-17 19:12 ` Philip Oakley
2016-09-17 19:21 ` Christian Couder
2016-09-18 10:21 ` Jakub Narębski
2016-09-18 10:51 ` Philip Oakley [this message]
2016-09-19 15:59 ` Junio C Hamano
2016-09-19 16:22 ` Philip Oakley
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=630656BFF8F84E43A2E4C67138A9A675@PhilipOakley \
--to=philipoakley@iee.org \
--cc=ajohnson388@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=iveqy@iveqy.com \
--cc=jnareb@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).