From: "Pádraig Brady" <P@draigBrady.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Linus Torvalds <torvalds@osdl.org>,
Junio C Hamano <junkio@cox.net>,
Git Mailing List <git@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: What's in git.git and announcing v1.4.1-rc1
Date: Fri, 23 Jun 2006 15:04:56 +0100 [thread overview]
Message-ID: <449BF508.9040207@draigBrady.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0606231305000.29667@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
> Hi,
>
> On Thu, 22 Jun 2006, Linus Torvalds wrote:
>
>
>>On Thu, 22 Jun 2006, Junio C Hamano wrote:
>>
>>> - diff --color (Johannes).
>>
>> - default to red/green for old/new lines. That's the norm, I'd think.
>
>
> ... and which happens to be useless for 10% of the male population (and
> even more if you look specifically at Asian people). But then, I just
> pasted that part from somewhere else.
:)
So 10% of the male population need to learn
traffic light positions rather than colours?
I'm red/green colour blind which means I can't
distinguish _subtley_ different shades of red and green.
vim is another fondue fork offender as it merges
syntax highlighting and diff colours in diff mode (vimdiff).
I put the following in ~/.vimrc to disable that madness:
if &diff
"I'm only interested in diff colours
syntax off
endif
Pádraig.
next prev parent reply other threads:[~2006-06-23 14:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 19:49 Junio C Hamano
2006-06-22 20:21 ` Paolo Ciarrocchi
2006-06-22 20:53 ` Linus Torvalds
2006-06-22 20:58 ` Petr Baudis
2006-06-22 21:02 ` Linus Torvalds
2006-06-22 21:24 ` Jakub Narebski
2006-06-22 21:28 ` Petr Baudis
2006-06-23 11:10 ` Johannes Schindelin
2006-06-23 11:10 ` Johannes Schindelin
2006-06-23 14:04 ` Pádraig Brady [this message]
2006-06-23 14:25 ` Johannes Schindelin
2006-06-23 14:59 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=449BF508.9040207@draigBrady.com \
--to=p@draigbrady.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®