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

Poor status output during conflicted merge

From
EREric Raible <raible@gmail.com>
Date
Jul 1, 2010, 18:16 UTC
Message-ID
<loom.20100701T195742-266@post.gmane.org>
Let's create a merge conflict and then partially resolve it:

git init bad-status cd bad-status/ echo 1 > file git add file git commit -a -m1 echo 2 > file git commit -a -m2 git checkout -b topic HEAD^ echo 3 > file git commit -a -m3 git merge master git checkout --ours file git add file

A 'git status' at this point gives the following output:

# On branch topic nothing to commit (working directory clean)

Which is wrong, since the merge still needs to be committed.
- Eric
Next: Junio C Hamano
Message 1 of 6 in “Poor status output during conflicted merge”
  1. Eric RaibleJul 1, 2010
  2. Junio C HamanoJul 2, 2010
  3. Eric RaibleJul 2, 2010
  4. Eric RaibleJul 7, 2010
  5. Elijah NewrenJul 7, 2010
  6. demerphqJul 7, 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.