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

Re: Bug report: git-stash doesn't return correct status code

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 7, 2018, 18:58 UTC
Message-ID
<xmqqzi3jzp91.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<8ED425DE0F8BEC45AADD477A8872875788FB691C@hasmsx109.ger.corp.intel.com>
"Vromen, Tomer" <tomer.vromen@intel.com> writes:
Show 6 quoted lines
>> git stash && git checkout -b new-feature-branch && git stash pop
>
> This is useful when I realize that I want to open a new branch for my changes (that I haven't committed yet).
> However, I might have forgotten to save my changes in the editor, so git-stash will give this error:
>
> No local changes to save

This is given with "say" and not with "die", as this is merely an informational diagnosis. The command did not find any erroneous condition, the command did not fail to do anything it was supposed to do, so the command exited with 0 status.

Previous: Vromen, TomerNext: Junio C Hamano
Message 2 of 4 in “Bug report: git-stash doesn't return correct status code”
  1. Vromen, TomerMar 7, 2018
  2. Junio C HamanoMar 7, 2018
  3. Junio C HamanoMar 7, 2018
  4. Vromen, TomerMar 8, 2018

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.