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, 09:35 UTC
Message-ID
<20080222093558.GC29114@artemis.madism.org>
In-Reply-To
<20080221230101.27644.49229.stgit@gandelf.nowhere.earth>
On Thu, Feb 21, 2008 at 11:01:28PM +0000, Yann Dirson wrote:
> Signed-off-by: Yann Dirson <ydirson@altern.org>
> Cc: Pierre Habouzit <madcoder@debian.org>
> +If the constraints imposed by the use of `git rev-parse` do not fit
> +for a particular tool, `USAGE` (and `LONG_USAGE`, if any) can be used
> +to define message given by `usage()` shell function; no command-line
> +pre-processing occurs, the script has entire control over it.
  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™
  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 !
-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org
Previous: Yann DirsonNext: Junio C Hamano
Message 2 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.