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

Re: git status during interactive rebase

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 21, 2016, 09:28 UTC
Message-ID
<alpine.DEB.2.20.1601211016140.2964@virtualbox>
In-Reply-To
<CAGZ79kbUwJ+CN=YoQUP=rm=EhU=fU2ynt_7Q-cd7Dic-bsx+TA@mail.gmail.com>
Hi Stefan,
On Wed, 20 Jan 2016, Stefan Beller wrote:
> So I ran an interactive rebase, and while editing
> .git/rebase-merge/git-rebase-todo I tried to run
> `git status` in another terminal to inquire about a
> filename of an untracked file.

Heh, I don't think that anybody did that before, because the rebase has not even quite started yet...

The cop-out would be to write an empty 'done' file before editing the todo, but it would give the wrong impression that it is safe to run `git rebase --continue` now... Interactive rebase is *definitely* not thread-safe ;-)

So the proper fix might be to test for the presence of the "done" file and otherwise tell the user that this rebase has not even started yet.

Ciao, Dscho

Previous: Johannes Schindelin
Message 6 of 6 in “git status during interactive rebase”
  1. Stefan BellerJan 20, 2016
  2. Matthieu MoyJan 21, 2016
  3. Stefan BellerJan 21, 2016
  4. Junio C HamanoJan 21, 2016
  5. Johannes SchindelinJan 22, 2016
  6. Johannes SchindelinJan 21, 2016

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.