From: Mike Frysinger <vapier@gentoo.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: hjk@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uio-howto.tmpl: use standard copyright/legal markings
Date: Tue, 24 Jun 2008 05:45:18 -0400 [thread overview]
Message-ID: <200806240545.19494.vapier@gentoo.org> (raw)
In-Reply-To: <20080624002005.defb45d3.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
On Tuesday 24 June 2008, Andrew Morton wrote:
> On Sun, 22 Jun 2008 23:12:42 -0400 Mike Frysinger <vapier@gentoo.org> wrote:
> > The Userspace I/O HOWTO document uses straight <sect1> tags and plain
> > text to describe copyright/legal information. It should instead use the
> > <copyright> and <legalnotice> tags like all other documents in the
> > kernel.
>
> There are conflicting changes in this file in linux-next.
i'll take a look
> > + <holder>Hans-J__rgen Koch.</holder>
> > - Copyright (c) 2006 by Hans-J__rgen Koch.</para>
>
> Oh dear, that got mangled at your end, or in transmission. It seems to
> be mangled in mainline too. This happens a lot.
i doubt it was on my end since i didnt modify the code, but i dont think it's
mangled either. it looks like a standard UTF8 umlaut to me.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2008-06-24 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 3:12 [PATCH] uio-howto.tmpl: use standard copyright/legal markings Mike Frysinger
2008-06-24 7:20 ` Andrew Morton
2008-06-24 9:45 ` Mike Frysinger [this message]
2008-06-24 10:53 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2008-06-24 10:54 Mike Frysinger
2008-06-24 13:42 ` Hans J. Koch
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=200806240545.19494.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=akpm@linux-foundation.org \
--cc=hjk@linutronix.de \
--cc=linux-kernel@vger.kernel.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