git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Federico Lucifredi <flucifredi@acm.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Suggestion: "man git clone"
Date: Thu, 21 Aug 2008 16:07:46 -0700	[thread overview]
Message-ID: <48ADF542.9010105@zytor.com> (raw)
In-Reply-To: <48ADE2FF.4080704@acm.org>

Federico Lucifredi wrote:
> Hello HP,
>  I have seen this in (funnily enough) a project I manage myself, which 
> has subcommands structured similarly to Git.
> 
>  I have looked at options, but so far the current behavior (man foo-bar) 
> seems the best option for foo's subcommand bar. The alternative, also 
> acceptable, is a large page with subsections for each command. Sections 
> (man 1) are used for chapter-like page groupings, not for subsections on 
> a single command - those would have to be implemented as an additional 
> layer.
> 
>  But, as another participant in the thread has commented, that would not 
> port to other platforms very quickly (although it would get to Linux and 
> OS-X promptly, and may eventually make its way into other platforms).
> 
>  I am open to ideas, but so far the two options above are better than 
> anything else that has been so far suggested...
> 

One option would be to support "man foo bar" showing the page labelled 
foo-bar.  That way you'd get at least a modicum of bass-ackwards 
compatibility.

However, at some point we have to be willing to do things other 
platforms won't, or we'll never do anything new...

	-hpa

  reply	other threads:[~2008-08-21 23:09 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 [this message]
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
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=48ADF542.9010105@zytor.com \
    --to=hpa@zytor.com \
    --cc=flucifredi@acm.org \
    --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).