From: Junio C Hamano <gitster@pobox.com>
To: Pierre Habouzit <madcoder@debian.org>
Cc: Yann Dirson <ydirson@altern.org>, git@vger.kernel.org
Subject: Re: [PATCH] Improve documentation for git-sh-setup.
Date: Fri, 22 Feb 2008 09:17:51 -0800 [thread overview]
Message-ID: <7vbq68ap1c.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 20080222093558.GC29114@artemis.madism.org
Pierre Habouzit <madcoder@debian.org> writes:
> Actually, new scripts should be written using git rev-parse if
> possible, the USAGE/LONG_USAGE were there _before_ and I'd like to call
> them the deprecated interface if other git hackers don't mind.
>
> git rev-parse --parseopt gives consistency in how git parses options,
> and it's A Good Thing™
I certainly think encouraging use of parse-options in new
scripts is a good idea, even though I suspect "deprecated" above
might be a bit too strong.
I did not find accessible from the command line variant was the
parse-opt-hidden feature, which was frustrating.
> That makes me think that git-sh-setup(1) use should be documented in
> gitcli(5), maybe even included, and git-sh-setup(1) should *definitely*
> link to gitcli(5). We wondered where to link gitcli from, this is
> definitely the place !
Sounds good. Please make it so.
next prev parent reply other threads:[~2008-02-22 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 23:01 [PATCH] Improve documentation for git-sh-setup Yann Dirson
2008-02-22 9:35 ` Pierre Habouzit
2008-02-22 17:17 ` Junio C Hamano [this message]
2008-02-22 18:19 ` Pierre Habouzit
2008-02-23 14:09 ` [PATCH] parse-opt: bring PARSE_OPT_HIDDEN to git-rev-parse --parseopt Pierre Habouzit
2008-02-24 8:42 ` Junio C Hamano
2008-02-24 8:49 ` Pierre Habouzit
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=7vbq68ap1c.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.org \
--cc=ydirson@altern.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).