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

Re: [PATCH 1/2] sh-setup: Write a new require_clean_work_tree function

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Sep 26, 2010, 17:39 UTC
Message-ID
<20100926173956.GA15143@kytes>
In-Reply-To
<vpqmxr4piyf.fsf@bauges.imag.fr>
Hi Matthieu,
Matthieu Moy writes:
> I totally agree on the idea, and the implementation is OK. On the
> format of the message, you can try to make it more consistent with
> other error messages, like:
Thanks for the review.
Show 11 quoted lines
> $ git merge branch
> error: The following untracked working tree files would be overwritten by merge:
>         one
> 	two
> Please move or remove them before you can merge.
> 
> That would give stg like:
> 
> echo >&2 "error: The following files have unstaged changes:"
> git diff-files --name-status -r --ignore-submodules -- >&2
> echo >&2 "Please commit or stash them to proceed."
Ok, sounds good.
> Also, you probably want to give all the error before you "exit 1",
> hence stg like:

Hm, is that a good idea? We want the output to be functional and indicative: it should tell the user what to do immediately. I'm afraid that displaying both errors will make the output very verbose. We can just tell the user about the unstaged changes, and wait for them to commit or stash it. Either way, both commit and stash will affect the index by default :)

-- Ram
Previous: Matthieu MoyNext: Matthieu Moy
Message 8 of 12 in “What exactly does 'needs update' mean?”
  1. Joshua JensenSep 25, 2010
  2. Junio C HamanoSep 25, 2010
  3. Joshua JensenSep 25, 2010
  4. Joshua JensenSep 25, 2010
  5. 0/2 Eliminate cryptic "needs update" error messageRamkumar Ramachandra, Sep 26, 2010
  6. 1/2 sh-setup: Write a new require_clean_work_tree functionRamkumar Ramachandra, Sep 26, 2010
  7. Matthieu MoySep 26, 2010
  8. Ramkumar RamachandraSep 26, 2010
  9. Matthieu MoySep 26, 2010
  10. Ramkumar RamachandraSep 26, 2010
  11. 2/2 Porcelain scripts: Rewrite cryptic "needs update" error messageRamkumar Ramachandra, Sep 26, 2010
  12. Matthieu MoySep 26, 2010

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.