linux-kernel - Re: 463 kernel developers missing!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9e4733910807281119m10f9b6e3v98fc892a42476c86@mail.gmail.com>
Date:	Mon, 28 Jul 2008 14:19:56 -0400
From:	"Jon Smirl" <jonsmirl@...il.com>
To:	"Simon Arlott" <simon@...e.lp0.eu>
Cc:	lkml <linux-kernel@...r.kernel.org>
Subject: Re: 463 kernel developers missing!

On 7/28/08, Simon Arlott <simon@...e.lp0.eu> wrote:
> On 28/07/08 18:22, Jon Smirl wrote:
>
> > On 7/28/08, Simon Arlott <simon@...e.lp0.eu> wrote:
> >
> > > On 28/07/08 18:05, Jon Smirl wrote:
> > > > On 7/28/08, Simon Arlott <simon@...e.lp0.eu> wrote:
> > > > >  Just because anyone can grep the kernel log for email addresses [to
> > > send
> > > > > spam to], doesn't mean that you need to do it for them.
> > > > >
> > > >
> > > > You need to be in the file since you have submitted patches using
> three
> > > aliases.
> > > >
> > >
> > >  No, I've submitted patches using three email addresses (well, two - one
> is
> > > a typo).
> > >
> >
> > That's the whole point of this list. When you submit patches in the
> > future we can check your name/email against the list and flag it if it
> > isn't there. That will alert you that you've made a typo.
> >
>
>  I don't make typos in my name or email address.

You just admitted six lines early that you made a typo.

> > A later version of this list could separate the valid current
> > names/addresses from the entries that are fixing typos or that have
> > old emails. That would improve the validation. But I don't have an
> > automated way to tell me which alias is the current one. Access to the
> > current LKML subscriber list would supply the needed info as to which
> > one to pick.
> >
>
>  Validation of what?
>  The current alias is the most recent active one.
>
>  I'm not subscribed to the LKML with a public address.
>  Please Cc: me if you submit a patch for this so I can add a Nacked-By:
> and/or cleanup the list by removing redundant entires. Even if git-shortlog
> is changed to distinguish between people who share the same name, it would
> still be a list of exceptions rather than everyone.

Comparing to LKML subscribers would not be used to generate new email
addresses. It would only help to identify which existing alias is your
current one.  But we don't have to do it that way, I can use the email
of your most recent commit as your current address and you can fix it
if it is wrong. Only email addresses that appear in the kernel log
should appear in the mailmap file.


>
>  --
>  Simon Arlott
>


-- 
Jon Smirl
jonsmirl@...il.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/