All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Webb <chris@arachsys.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH v3 2/3] Allow help.htmlpath to be a URL prefix
Date: Fri, 29 Jun 2012 00:38:30 +0100	[thread overview]
Message-ID: <20120628233830.GA2765@arachsys.com> (raw)
In-Reply-To: <7vvcib3zam.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

> Sounds sensible and looks reasonable.  Thanks.

Great! Glad they were of interest.

> I do not think [PATCH 3/3] is a positive change at all, though.

Yes, I think my aversion for being thrown into the full manual with
git foo --help is quite unusual, so this one's probably better left
as one of my idiosyncratic local patches.

The reason I thought there was a chance this could be of wider interest is
that, on a machine without man pages,

  $ git show --help
  warning: failed to exec 'man': No such file or directory
  fatal: no man viewer handled the request

is a bit unfriendly when git actually has enough internal help to be able to
offer

  $ git show -h    
  usage: git log [<options>] [<since>..<until>] [[--] <path>...]
     or: git show [options] <object>...

...but only if you know that -h exists and is not a synonym for --help.

Cheers,

Chris.

  reply	other threads:[~2012-06-28 23:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28  6:58 [PATCH v3 1/3] Add config variable to set HTML path for git-help --web Chris Webb
2012-06-28  6:58 ` [PATCH v3 2/3] Allow help.htmlpath to be a URL prefix Chris Webb
2012-06-28 21:24   ` Junio C Hamano
2012-06-28 23:38     ` Chris Webb [this message]
2012-06-28  6:58 ` [PATCH v3 3/3] Add a help format 'usage' to provide brief command usage Chris Webb
2012-06-28 21:39 ` [PATCH v3 1/3] Add config variable to set HTML path for git-help --web Junio C Hamano

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=20120628233830.GA2765@arachsys.com \
    --to=chris@arachsys.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.