From: Keith Packard <keithp@keithp.com>
To: Junio C Hamano <junkio@cox.net>
Cc: keithp@keithp.com, Tommi Virtanen <tv@debian.org>, git@vger.kernel.org
Subject: Re: [PATCH] git-mktree: reverse of git-ls-tree.
Date: Mon, 20 Feb 2006 22:52:30 -0800 [thread overview]
Message-ID: <1140504750.16926.111.camel@evo.keithp.com> (raw)
In-Reply-To: <7vk6bp43qm.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
<internationalization-pedant-mode>
On Mon, 2006-02-20 at 22:37 -0800, Junio C Hamano wrote:
> + * Copyright (c) Junio C Hamano, 2006
I've been told by at least two lawyers that the string '(c)' has no
legal meaning in the US. If you want to indicate copyright, the only
symbol which does carry legal weight is the c-in-a-circle mark '©'.
Of course, this does force the issue of what encoding to present source
files in. I suggest that sources should be UTF-8, which also provides
opportunities to encode author names correctly, rather than
transliterating them to Latin. X.org uses UTF-8 for source files now
without difficulty across a wide range of compilers. Of course,
non-ascii glyphs are present only in comments.
</internationalization-pedant-mode>
--
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 6:53 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 [this message]
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
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=1140504750.16926.111.camel@evo.keithp.com \
--to=keithp@keithp.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=tv@debian.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;
as well as URLs for NNTP newsgroup(s).