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

Re: Poor status output during conflicted merge

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 2, 2010, 00:00 UTC
Message-ID
<7v1vbm3g8j.fsf@alter.siamese.dyndns.org>
In-Reply-To
<loom.20100701T195742-266@post.gmane.org>
Eric Raible <raible@gmail.com> writes:
Show 6 quoted lines
> 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.
It might be just a simple matter of ...
 wt-status.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/wt-status.c b/wt-status.c
index 2f9e33c..757536f 100644
--- a/wt-status.c
+++ b/wt-status.c
@@ -674,6 +674,8 @@ void wt_status_print(struct wt_status *s)
 			fprintf(s->fp, "# No changes\n");
 		else if (s->nowarn)
 			; /* nothing */
+		else if (s->in_merge)
+			printf("merge result will be the same as HEAD commit\n");
 		else if (s->workdir_dirty)
 			printf("no changes added to commit%s\n",
 				advice_status_hints
Previous: Eric RaibleNext: Eric Raible
Message 2 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.