From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?UTF-8?B?RGlyayBTw7xzc2Vyb3R0?= <newsletter@dirk.my1.cc>
Subject: Re: Meaning of double + and - in Gitk's diff pane
Date: Mon, 21 Mar 2011 20:57:17 +0100
Message-ID: <4D87AD9D.7080501@dirk.my1.cc>
References: <4D879B25.9090300@dirk.my1.cc> <7vr5a0p8n1.fsf@alter.siamese.dyndns.org> <4D87AAD6.6000704@dirk.my1.cc> <7vaagop83d.fsf@alter.siamese.dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Git Mailing List <git@vger.kernel.org>
To: Junio C Hamano <gitster@pobox.com>
X-From: git-owner@vger.kernel.org Mon Mar 21 21:01:27 2011
Return-path: <git-owner@vger.kernel.org>
Envelope-to: gcvg-git-2@lo.gmane.org
Received: from vger.kernel.org ([209.132.180.67])
	by lo.gmane.org with esmtp (Exim 4.69)
	(envelope-from <git-owner@vger.kernel.org>)
	id 1Q1lI7-00064f-2n
	for gcvg-git-2@lo.gmane.org; Mon, 21 Mar 2011 21:01:27 +0100
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754315Ab1CUUBW (ORCPT <rfc822;gcvg-git-2@m.gmane.org>);
	Mon, 21 Mar 2011 16:01:22 -0400
Received: from smtprelay01.ispgateway.de ([80.67.31.39]:57314 "EHLO
	smtprelay01.ispgateway.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752956Ab1CUUBV (ORCPT <rfc822;git@vger.kernel.org>);
	Mon, 21 Mar 2011 16:01:21 -0400
Received: from [84.176.60.154] (helo=[192.168.2.100])
	by smtprelay01.ispgateway.de with esmtpa (Exim 4.68)
	(envelope-from <newsletter@dirk.my1.cc>)
	id 1Q1lE7-00032T-Bi; Mon, 21 Mar 2011 20:57:19 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
In-Reply-To: <7vaagop83d.fsf@alter.siamese.dyndns.org>
X-Df-Sender: 757646
Sender: git-owner@vger.kernel.org
Precedence: bulk
List-ID: <git.vger.kernel.org>
X-Mailing-List: git@vger.kernel.org
Archived-At: <http://permalink.gmane.org/gmane.comp.version-control.git/169658>

Am 21.03.2011 20:49 schrieb Junio C Hamano:
>>
>> Junio, thanks. When I've found the time, I'll probably condense Linus'
>> explanations and submit a documentation patch. It's not explained
>> in the actual git docs, right?
>
> How about checking "git diff"?  The same conclusion should be in there, as
> I wrote the implementation, docs and the messages there.
>

Uhh, sorry, I missed that. That was actually what I was searching for.
Thanks.