git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Improve documentation for git-sh-setup.

From
Pierre Habouzit <madcoder@debian.org>
Date
Feb 22, 2008, 18:19 UTC
Message-ID
<20080222181927.GA4555@artemis.madism.org>
In-Reply-To
<7vbq68ap1c.fsf@gitster.siamese.dyndns.org>
On Fri, Feb 22, 2008 at 05:17:51PM +0000, Junio C Hamano wrote:
Show 12 quoted lines
> 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.
  Okay.
> I did not find accessible from the command line variant was the
> parse-opt-hidden feature, which was frustrating.
  Well, it's probably doable using some more magic flags, I can hack
something if you need to, I'll try to work something out during FOSDEM's
talks :)
Show 6 quoted lines
> >   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.
-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org
Previous: Junio C HamanoNext: Pierre Habouzit
Message 4 of 7 in “Improve documentation for git-sh-setup.”
  1. Improve documentation for git-sh-setup.Yann Dirson, Feb 21, 2008
  2. Pierre HabouzitFeb 22, 2008
  3. Junio C HamanoFeb 22, 2008
  4. Pierre HabouzitFeb 22, 2008
  5. parse-opt: bring PARSE_OPT_HIDDEN to git-rev-parse --parseoptPierre Habouzit, Feb 23, 2008
  6. Junio C HamanoFeb 24, 2008
  7. Pierre HabouzitFeb 24, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.