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

Re: [PATCH] git-pull.sh: Fix call to git-merge for new command format

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Dec 2, 2009, 17:29 UTC
Message-ID
<4B16A410.5090802@drmicha.warpmail.net>
In-Reply-To
<7vws15jpe7.fsf@alter.siamese.dyndns.org>
Junio C Hamano venit, vidit, dixit 02.12.2009 17:45:
Show 6 quoted lines
> Michael J Gruber <git@drmicha.warpmail.net> writes:
> 
>> This made me wonder a bit: Do we have a policy regarding the use of
>> "git-command" vs. "git command" in git shell scripts such as this one?
> 
> Yes.  Anything that sets GIT_EXEC_PATH correctly can use git-foo form.
I know they can. That was in the part you snipped ;)

The questions is: Should they? Should we avoid mixing both forms in one script?

Michael
Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 7 in “git-pull.sh: Fix call to git-merge for new command format”
  1. git-pull.sh: Fix call to git-merge for new command formatHorst H. von Brand, Dec 1, 2009
  2. Junio C HamanoDec 1, 2009
  3. Michael J GruberDec 2, 2009
  4. Junio C HamanoDec 2, 2009
  5. Michael J GruberDec 2, 2009
  6. Junio C HamanoDec 2, 2009
  7. Michael J GruberDec 3, 2009

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.