All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] linux-2.6.17-rc3-git13 fs/proc/array.c
Date: Mon, 08 May 2006 16:58:45 +0000	[thread overview]
Message-ID: <20060508165845.GB12272@parisc-linux.org> (raw)
In-Reply-To: <445EDBCA.9080702@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 955 bytes --]

On Mon, May 08, 2006 at 09:40:10AM -0700, Greg KH wrote:
> On Mon, May 08, 2006 at 08:18:08AM -0700, Nishanth Aravamudan wrote:
> > On 08.05.2006 [03:27:10 -0400], Anne Thrax wrote:
> > > I would rather not use my real name, as I am only 14 years old.
> > 
> > I'm not sure I entirely understand how the one stems from the other, but
> > I think the spirit of the "personal information" part of the DCO
> > (Developer's Certificate of Origin, in Documentation/SubmittingPatches)
> > is something like full disclosure. Also, I wonder how, if at all, the
> > DCO can be enforced when it involves a minor. I'll defer to Greg on this
> > one... at least on whatever precedent exists, I don't expect a legal
> > decision, Greg :)
> 
> Doesn't matter, we still need a real name.  It's not a legal issue but a
> "trace the blame" issue.

A pseudonym + email address performs acceptably for "trace the blame".
So I don't see how your two statements are related.


[-- Attachment #2: Type: text/plain, Size: 168 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2006-05-08 16:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08  5:48 [KJ] [PATCH] linux-2.6.17-rc3-git13 fs/proc/array.c Anne Thrax
2006-05-08  6:44 ` Nishanth Aravamudan
2006-05-08  7:27 ` Anne Thrax
2006-05-08 15:18 ` Nishanth Aravamudan
2006-05-08 16:40 ` Greg KH
2006-05-08 16:58 ` Nishanth Aravamudan
2006-05-08 16:58 ` Matthew Wilcox [this message]
2006-05-08 17:49 ` Greg KH
2006-05-09 19:37 ` Matthew Wilcox
2006-05-09 19:44 ` Alexey Dobriyan
2006-05-10 22:15 ` Randy.Dunlap
2006-05-11  0:46 ` Nishanth Aravamudan

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=20060508165845.GB12272@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=kernel-janitors@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 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.