git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Avery Pennarun" <apenwarr@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "\"Peter Valdemar Mørch (Lists)\"" <4ux6as402@sneakemail.com>,
	flucifredi@acm.org, "Git ML" <git@vger.kernel.org>
Subject: Re: Suggestion: "man git clone"
Date: Thu, 21 Aug 2008 13:07:14 -0400	[thread overview]
Message-ID: <32541b130808211007xf295e40l567ecf785a8fca22@mail.gmail.com> (raw)
In-Reply-To: <48AD99DF.5090802@zytor.com>

On Thu, Aug 21, 2008 at 12:37 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> man git clone
>
> [...]
>
> I doubt you find *anyone* who relies on the current behaviour, so I am
> suggesting changing man.  That's why the man author was on the recipient
> list, but you removed it.
>

[and I put him back...]

Unfortunately what we don't have is a proposal that would work better.
 Also, changing the behaviour of 'man' wouldn't work on any platform
other than Linux (presumably), which means the git documentation
wouldn't be able to rely on that behaviour.

Still, in a perfect world, what *should* man do in such a case?
Automatically open /usr/man/man1/git/clone.1?

Thanks,

Avery

  reply	other threads:[~2008-08-21 17:08 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 [this message]
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
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=32541b130808211007xf295e40l567ecf785a8fca22@mail.gmail.com \
    --to=apenwarr@gmail.com \
    --cc=4ux6as402@sneakemail.com \
    --cc=flucifredi@acm.org \
    --cc=git@vger.kernel.org \
    --cc=hpa@zytor.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. 
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).