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

Re: [PATCH] Stop telling users we are 'defaulting to local storage area'.

From
Nicolas Pitre <nico@cam.org>
Date
Dec 15, 2006, 02:18 UTC
Message-ID
<Pine.LNX.4.64.0612142059301.18171@xanadu.home>
In-Reply-To
<20061214230902.GA26506@spearce.org>
On Thu, 14 Dec 2006, Shawn O. Pearce wrote:
[...]
> It also breaks from our normal behavior of not printing
> anything if the command was successful.

Before everybody starts believing everybody agrees with this I'll have to throw a tile in the pond.

I really don't think this is a good rule.

NOte that I'm not against commands that are silent by default. I really think that git-add should remain silent on success by default when successful.

But the rule of thumb should be about the importance of the action performed by the command. git-add is a less important command than git-init-db or git-commit _conceptually_. You can do multiple git-add in whatever order, even repeatedly, and it won't change the outcome. It is "conceptually lightweight". But git-init-db is really important. Without it you just can't do anything. It should give the user the impression that something did actually happen, especially since this is the git comand any new git user is most likely to use first. Saying back "git repository initialized" tells the user "OK you can start now". Saying nothing might just leave the user wondering if everything is actually fine.

Previous: Shawn O. PearceNext: Shawn Pearce
Message 2 of 5 in “Stop telling users we are 'defaulting to local storage area'.”
  1. Stop telling users we are 'defaulting to local storage area'.Shawn O. Pearce, Dec 14, 2006
  2. Nicolas PitreDec 15, 2006
  3. Shawn PearceDec 15, 2006
  4. David LangDec 19, 2006
  5. Jakub NarebskiDec 15, 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.