Git development
 help / color / mirror / Atom feed
* [PATCH] Documentation: clarify commits affected by gitk --merge
@ 2009-02-06  4:40 Sitaram Chamarty
  2009-02-07 21:45 ` Junio C Hamano
  0 siblings, 1 reply; 3+ messages in thread
From: Sitaram Chamarty @ 2009-02-06  4:40 UTC (permalink / raw)
  To: gitster; +Cc: git

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

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] Documentation: clarify commits affected by gitk --merge
  2009-02-06  4:40 [PATCH] Documentation: clarify commits affected by gitk --merge Sitaram Chamarty
@ 2009-02-07 21:45 ` Junio C Hamano
  2009-02-08  1:15   ` Sitaram Chamarty
  0 siblings, 1 reply; 3+ messages in thread
From: Junio C Hamano @ 2009-02-07 21:45 UTC (permalink / raw)
  To: Sitaram Chamarty; +Cc: git

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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] Documentation: clarify commits affected by gitk --merge
  2009-02-07 21:45 ` Junio C Hamano
@ 2009-02-08  1:15   ` Sitaram Chamarty
  0 siblings, 0 replies; 3+ messages in thread
From: Sitaram Chamarty @ 2009-02-08  1:15 UTC (permalink / raw)
  To: git

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-02-08  1:16 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-02-06  4:40 [PATCH] Documentation: clarify commits affected by gitk --merge Sitaram Chamarty
2009-02-07 21:45 ` Junio C Hamano
2009-02-08  1:15   ` Sitaram Chamarty

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox