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

[PATCH] Documentation: clarify commits affected by gitk --merge

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Feb 6, 2009, 04:40 UTC
Message-ID
<20090206044053.GA6831@atcmail.atc.tcs.com>
Signed-off-by: Sitaram Chamarty <sitaramc@gmail.com>
---

I remember being confused by this some weeks ago and someone clarified, so I thought I'd put it in.

 Documentation/gitk.txt |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/Documentation/gitk.txt b/Documentation/gitk.txt
index 4673a75..bd005bc 100644
--- a/Documentation/gitk.txt
+++ b/Documentation/gitk.txt
@@ -47,7 +47,8 @@ frequently used options.
 
 	After an attempt to merge stops with conflicts, show the commits on
 	the history between two branches (i.e. the HEAD and the MERGE_HEAD)
-	that modify the conflicted files.
+	that modify the conflicted files and do not exist on all the heads
+	being merged.
 
 --argscmd=<command>::
 	Command to be run each time gitk has to determine the list of
-- 
1.6.1
Next: Junio C Hamano
Message 1 of 3 in “Documentation: clarify commits affected by gitk --merge”
  1. Documentation: clarify commits affected by gitk --mergeSitaram Chamarty, Feb 6, 2009
  2. Junio C HamanoFeb 7, 2009
  3. Sitaram ChamartyFeb 8, 2009

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.