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

RE: [PATCH] git-explain

From
RBRaimund Bauer <ray@softwarelandschaft.com>
Date
Dec 5, 2006, 09:11 UTC
Message-ID
<001b01c7184d$5d142c20$0b0aa8c0@abf.local>
In-Reply-To
<7v1wnekh6a.fsf@assigned-by-dhcp.cox.net>
> An issue with this approach is that this can be the beginning 
> of hardwiring the official "right way of doing things" in the 
> set of tools.  Pursuing this approach would enhance the set 
> of state markers like "FAILED_MERGE" in the example, which means:

Wouldn't it be better to create some kind of action-log (that's cleared at the end of the command if everything was all right) instead of creating special markers for different commands?

That way there would be only 1 place to check for what happened ...
-- 
best regards

  Ray
Previous: J. Bruce Fields
Message 7 of 7 in “Re: [PATCH] git-explain”
  1. Nicolas PitreDec 5, 2006
  2. J. Bruce FieldsDec 5, 2006
  3. Junio C HamanoDec 5, 2006
  4. Jeff KingDec 5, 2006
  5. Johannes SchindelinDec 5, 2006
  6. J. Bruce FieldsDec 5, 2006
  7. Raimund BauerDec 5, 2006

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.