From: Keith Packard <keithp@keithp.com>
To: Junio C Hamano <junkio@cox.net>
Cc: keithp@keithp.com, Andreas Ericsson <ae@op5.se>, git@vger.kernel.org
Subject: Re: [PATCH] git-mktree: reverse of git-ls-tree.
Date: Tue, 21 Feb 2006 09:23:48 -0800 [thread overview]
Message-ID: <1140542628.16926.125.camel@evo.keithp.com> (raw)
In-Reply-To: <7vr75x11or.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
On Tue, 2006-02-21 at 01:49 -0800, Junio C Hamano wrote:
> Keith is saying that unlike ciecle-c, (c) is meaningless. While
> he is right about that, it does not matter, as long as he is
> talking about "legal meaning in the US". It is my understanding
> that spelled out "Copyright" (or its abbreviation, "Copr.")
> weighs as much as the circle-c mark.
Precisely. I'd say either remove the (c) or replace it with the correct
symbol. As including the correct symbol requires selecting between an
8859 and 10646 encoding, one shows one's i18n-fu by including the © in
UTF-8.
Once this choice is firmly in place, the opportunties for excessive
character usage really flourish:
http://gitweb.freedesktop.org/?p=cairo;a=blobdiff;h=1c63adec9b6547c6446548dc3a877e1e4ba29bfd;hp=a6ebc5e04773c8b544cfb721b635ef5534be235f;hb=cc890b9cf4d2a38e13ae48e16589c4fd02678f99;f=src/cairo-pen.c
--
keith.packard@intel.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-02-21 17:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 6:37 [PATCH] git-mktree: reverse of git-ls-tree Junio C Hamano
2006-02-21 6:52 ` Keith Packard
2006-02-21 8:46 ` Andreas Ericsson
2006-02-21 9:49 ` Junio C Hamano
2006-02-21 10:20 ` Martin Langhoff
2006-02-21 17:23 ` Keith Packard [this message]
2006-02-21 17:57 ` Linus Torvalds
2006-02-21 17:40 ` Linus Torvalds
2006-02-21 17:46 ` Keith Packard
2006-02-21 18:00 ` 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=1140542628.16926.125.camel@evo.keithp.com \
--to=keithp@keithp.com \
--cc=ae@op5.se \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).