From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Fix git_config_set() for mean cases
Date: 16 Nov 2005 17:40:20 -0800 [thread overview]
Message-ID: <86br0kjbln.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0511170013470.9284@wbgn013.biozentrum.uni-wuerzburg.de>
>>>>> "Johannes" == Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Johannes> Besides, the character is there, so why not use it? ;-)
It reminds me of when people typed "l" instead of "1" because typewriters
didn't have a "1".
In that manner, it's just plain wrong.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2005-11-17 1:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 9:47 [PATCH] Fix git_config_set() for mean cases Johannes Schindelin
2005-11-16 20:21 ` Junio C Hamano
2005-11-16 20:52 ` H. Peter Anvin
2005-11-16 23:19 ` Johannes Schindelin
2005-11-17 1:40 ` Randal L. Schwartz [this message]
2005-11-16 23:26 ` Matthias Urlichs
[not found] ` <7vwtj847kj.fsf@assigned-by-dhcp.cox.net>
[not found] ` <Pine.LNX.4.63.0511170027380.9687@wbgn013.biozentrum.uni-wuerzburg.de>
[not found] ` <7vhdab3nlz.fsf@assigned-by-dhcp.cox.net>
[not found] ` <Pine.LNX.4.63.0511171115200.20898@wbgn013.biozentrum.uni-wuerzburg.de>
[not found] ` <7voe4jwm5w.fsf@assigned-by-dhcp.cox.net>
[not found] ` <Pine.LNX.4.63.0511171252070.737@wbgn013.biozentrum.uni-wuerzburg.de>
[not found] ` <7v1x1ful7j.fsf@assigned-by-dhcp.cox.net>
2005-11-17 21:10 ` Johannes Schindelin
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=86br0kjbln.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.