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

3 messages from 2009-02-06 to 2009-02-08. Participants: Sitaram Chamarty, Junio C Hamano.
Thread: https://gitlist.dev/t/17602

## Sitaram Chamarty, 2009-02-06 04:40

Subject: [PATCH] Documentation: clarify commits affected by gitk --merge
Message-ID: <20090206044053.GA6831@atcmail.atc.tcs.com>
URL: https://gitlist.dev/e/20090206044053.GA6831%40atcmail.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

```

## Junio C Hamano, 2009-02-07 21:45

Subject: Re: [PATCH] Documentation: clarify commits affected by gitk --merge
Message-ID: <7vtz75udj6.fsf@gitster.siamese.dyndns.org>
URL: https://gitlist.dev/e/7vtz75udj6.fsf%40gitster.siamese.dyndns.org
In-Reply-To: <20090206044053.GA6831@atcmail.atc.tcs.com>

```
Sitaram Chamarty <sitaramc@gmail.com> writes:

>  	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.

I do not understand what you are trying to add here, sorry.

```

## Sitaram Chamarty, 2009-02-08 01:15

Subject: Re: [PATCH] Documentation: clarify commits affected by gitk --merge
Message-ID: <slrngoscgp.qdh.sitaramc@sitaramc.homelinux.net>
URL: https://gitlist.dev/e/slrngoscgp.qdh.sitaramc%40sitaramc.homelinux.net
In-Reply-To: <7vtz75udj6.fsf@gitster.siamese.dyndns.org>

```
On 2009-02-07, Junio C Hamano <gitster@pobox.com> wrote:
> Sitaram Chamarty <sitaramc@gmail.com> writes:
>
>>  	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.
>
> I do not understand what you are trying to add here, sorry.

It's basically the same thing as the explanation for --merge
in 'git help log':
   --merge
       After a failed merge, show refs that touch files
       having a conflict and don´t exist on all heads to
       merge.

I'm pretty sure gitk is doing the same thing, so I thought
the extra text should be added.

Regards,

Sitaram

```