All of lore.kernel.org
 help / color / mirror / Atom feed
From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] linux-2.6.17-rc3-git13
Date: Tue, 09 May 2006 08:00:50 +0000	[thread overview]
Message-ID: <44604C32.7000509@bfs.de> (raw)
In-Reply-To: <445EF28A.1010601@bfs.de>


hi,
i read that some parents in the US force there children not to reveal 
the identify online. This is a problem for the kids.
To help i think they should tell there read identify a trustee and
get a bogus name what appears in the logs. forcing them to reveal
will cause only trouble.

my 2 cents,
  walter



Greg KH wrote:
> On Mon, May 08, 2006 at 10:58:45AM -0600, Matthew Wilcox wrote:
>> 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.
> 
> It's a matter of trust.  If you want to trust us to take your changes,
> you need to show that you trust us enough to be willing to accept
> recgonition for those changes.  By using a pseudonym, you are not
> showing a whole lot of trust, and by using it, it take a whole lot more
> effort to get that trust.
> 
> That being said, there are a few pseudonyms out there that I do trust,
> just because they have been around for years and show that they are
> trustworthy people.
> 
> thanks,
> 
> greg k-h
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Kernel-janitors mailing list
> Kernel-janitors@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/kernel-janitors
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

  reply	other threads:[~2006-05-09  8:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08  7:26 [KJ] [PATCH] linux-2.6.17-rc3-git13 walter harms
2006-05-09  8:00 ` walter harms [this message]
2006-05-09  8:13 ` Greg KH
2006-05-09  9:36 ` walter harms
2006-05-11  1:47 ` Anne Thrax

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=44604C32.7000509@bfs.de \
    --to=wharms@bfs.de \
    --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.