From: Junio C Hamano <gitster@pobox.com>
To: "Philip Oakley" <philipoakley@iee.org>
Cc: "Git List" <git@vger.kernel.org>
Subject: Re: Improve 'git help' with basic user guide linkss
Date: Fri, 08 Feb 2013 14:54:50 -0800 [thread overview]
Message-ID: <7v6222za9x.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <6BC280F5827C4098BCB6276232DDE8E4@PhilipOakley> (Philip Oakley's message of "Fri, 8 Feb 2013 21:43:38 -0000")
"Philip Oakley" <philipoakley@iee.org> writes:
> My initial https://github.com/PhilipOakley/git/commit/e6217d simply
> updates
> - N_("See 'git help <command>' for more information on a specific
> command.");
> + N_("See 'git help <command>' for more information on a specific
> command.\n"
> + "Or 'git help <guide>', such as 'tutorial' for an introduction
> to Git.");
> as a starter for the new users.
Yeah, that would be a good change to make to "git help<RETURN>"
output.
> My view is that help --all (-a) is essentially incomplete as it
> currently doesn't provide all the help.
It has always been about "tell me all subcommands", not about "give
me all the help you could give me". You are not adding a "help"
subcommand to a system you wrote last week. Changing the semantics
this late feels, eh, too late.
next prev parent reply other threads:[~2013-02-08 22:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 20:28 Improve 'git help' with basic user guide linkss Philip Oakley
2013-02-08 20:53 ` Junio C Hamano
2013-02-08 21:43 ` Philip Oakley
2013-02-08 22:54 ` Junio C Hamano [this message]
2013-02-08 23:16 ` Philip Oakley
2013-02-12 11:11 ` Philip Oakley
2013-02-12 11:37 ` John Keeping
2013-02-12 12:00 ` Philip Oakley
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=7v6222za9x.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.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