From: "Mikael Magnusson" <mikachu@gmail.com>
To: "Michael J Gruber" <michaeljgruber+gmane@fastmail.fm>
Cc: git@vger.kernel.org
Subject: Re: Suggestion: "man git clone"
Date: Fri, 22 Aug 2008 17:53:45 +0200 [thread overview]
Message-ID: <237967ef0808220853k24b2d969l55d04ec13bd7c8c9@mail.gmail.com> (raw)
In-Reply-To: <g8m6d1$7nf$1@ger.gmane.org>
2008/8/22 Michael J Gruber <michaeljgruber+gmane@fastmail.fm>:
> H. Peter Anvin venit, vidit, dixit 21.08.2008 02:11:
>> Given the recent change of "git-foo" to "git foo", it would be really
>> nice if one could type, for example:
>>
>> man git clone
>>
>> and actually get the man page for the git clone command. There are
>> quite a few other pieces of software which also could benefit from that
>> kind of indirection.
>>
>> Right now the above command shows the man page git(1) followed by
>> clone(2), which I believe has be classified as utterly useless behaviour...
>
> The discussion seems to show that altering man and relying on the new
> behaviour is no option, and neither is playing games with man's section
> options.
>
> How about:
>
> - Change all references in the help pages (gitlinks) accordingly.
I think that would break navigating man pages in any man reader... Most of
them detect and handle "foo(N)" magically and let you click on it.
--
Mikael Magnusson
next prev parent reply other threads:[~2008-08-22 15:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 0:11 Suggestion: "man git clone" H. Peter Anvin
2008-08-21 0:25 ` "Peter Valdemar Mørch (Lists)"
2008-08-21 16:37 ` H. Peter Anvin
2008-08-21 17:07 ` Avery Pennarun
2008-08-21 17:22 ` H. Peter Anvin
2008-08-21 17:38 ` Jeff King
2008-08-21 20:13 ` Jeff King
2008-08-21 20:14 ` H. Peter Anvin
2008-08-21 20:18 ` Jeff King
2008-08-21 17:52 ` Bert Wesarg
2008-08-22 11:37 ` A Large Angry SCM
2008-08-21 21:49 ` Federico Lucifredi
2008-08-21 23:07 ` H. Peter Anvin
2008-08-22 0:07 ` Federico Lucifredi
2008-08-22 0:40 ` Jeff King
2008-08-22 0:42 ` Jeff King
2008-08-22 1:15 ` Miklos Vajna
2008-08-22 1:21 ` Jeff King
2008-08-22 1:21 ` Federico Lucifredi
2008-08-22 1:19 ` Federico Lucifredi
2009-06-28 2:34 ` Colin Watson
2009-07-06 2:48 ` Federico Lucifredi
2009-07-06 4:11 ` Federico Lucifredi
2008-09-04 2:22 ` Federico Lucifredi
2008-09-04 3:31 ` H. Peter Anvin
2008-08-22 11:02 ` Michael J Gruber
2008-08-22 15:03 ` Derek Fawcus
2008-08-22 15:53 ` Mikael Magnusson [this message]
2008-08-25 12:38 ` Matthieu Moy
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=237967ef0808220853k24b2d969l55d04ec13bd7c8c9@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=git@vger.kernel.org \
--cc=michaeljgruber+gmane@fastmail.fm \
/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).