From: Federico Lucifredi <flucifredi@acm.org>
To: Jeff King <peff@peff.net>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Suggestion: "man git clone"
Date: Thu, 21 Aug 2008 21:19:56 -0400 [thread overview]
Message-ID: <48AE143C.8030704@acm.org> (raw)
In-Reply-To: <20080822004052.GA30476@coredump.intra.peff.net>
Jeff King wrote:
> On Thu, Aug 21, 2008 at 08:07:56PM -0400, Federico Lucifredi wrote:
>
>> I am all for bass-ackwards compatibility, and I think the suggestion of
>> going on "man foo bar" :
>>
>> 1) look for foo-bar; if success, terminate search
>> 2) look for foo
>> 3) look for bar
>> ....
>>
>> may be acceptable - I don't see drawbacks at a first glance, and it would
>> allow for groups of pages to be meaningful.
>
> Well, the drawback is that there exist X-Y such that X and Y both have
> manpages (e.g., cvs-debc on my debian box). So we are assuming that the
> risk is acceptably low of somebody asking for "man X Y", wanting two
> manpages, and that X and Y fit this pattern.
>
That's right.
> Personally I have never ever wanted to see two manpages from one man
> invocation, so I have no real problem with that assumption.
>
I expected as much, and we should have an option to disable the "new"
behavior as a safety anyway.
>> Are you willing to put your patch where your mouth is? :-)
>
> I've never looked at man code before, but there seem to be at least two
> man packages for Linux. My boxes have man-db 2.5.2.
There are two man packages for linux, man and man-db, the latter being a
90's fork that uses Berkeley DB as a backend to speedup man -k searches
(it helped back then).
Best -F
--
_________________________________________
-- "'Problem' is a bleak word for challenge" - Richard Fish
(Federico L. Lucifredi) - flucifredi@acm.org
next prev parent reply other threads:[~2008-08-22 1:21 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 [this message]
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=48AE143C.8030704@acm.org \
--to=flucifredi@acm.org \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.