linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Harry Wei <harryxiyou@gmail.com>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Brian Warner <brian.warner@samsung.com>,
	"David S. Miller" <davem@davemloft.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	"Gustavo A. R. Silva" <garsilva@embeddedor.com>,
	Benoit Parrot <bparrot@ti.com>, Al Viro <viro@zeniv.linux.org.uk>,
	Arvind Yadav <arvind.yadav.cs@gmail.com>,
	Kees Cook <keescook@chromium.org>,
	Bhumika Goyal <bhumirks@gmail.com>, Sean Young <sean@mess.org>,
	Brad Love <brad@nextdimension.cc>,
	Devin Heitmueller <dheitmueller@kernellabs.com>,
	Philippe Ombredanne <pombredanne@nexb.com>,
	Markus Elfring <elfring@users.sourceforge.net>,
	Alexey Klimov <klimov.linux@gmail.com>,
	Colin Ian King <colin.king@canonical.com>,
	Julia Lawall <Julia.Lawall@lip6.fr>,
	Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Tim Harvey <tharvey@gateworks.com>,
	Tomasz Figa <tfiga@chromium.org>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Yong Zhi <yong.zhi@intel.com>, Jan Kara <jack@suse.cz>,
	Dan Williams <dan.j.williams@intel.com>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Kamil Rytarowski <n54@gmx.com>,
	Matthew Wilcox <mawilcox@microsoft.com>,
	linux-doc@vger.kernel.org, linux-kernel@zh-kernel.org,
	Mauro Carvalho Chehab <mchehab@s-opensource.com>
Subject: Re: [PATCH] MAINTAINERS & files: Canonize the e-mails I use at files
Date: Fri, 4 May 2018 08:33:55 -0300	[thread overview]
Message-ID: <20180504083355.0c891ab3@vento.lan> (raw)
In-Reply-To: <87in837km8.fsf@intel.com>

Em Fri, 04 May 2018 13:58:39 +0300
Jani Nikula <jani.nikula@linux.intel.com> escreveu:

> On Fri, 04 May 2018, Mauro Carvalho Chehab <mchehab+samsung@kernel.org> wrote:
> > From now on, I'll start using my @kernel.org as my development e-mail.
> >
> > As such, let's remove the entries that point to the old
> > mchehab@s-opensource.com at MAINTAINERS file.
> >
> > For the files written with a copyright with mchehab@s-opensource,
> > let's keep Samsung on their names, using mchehab+samsung@kernel.org,
> > in order to keep pointing to my employer, with sponsors the work.
> >
> > For the files written before I join Samsung (on July, 4 2013),
> > let's just use mchehab@kernel.org.
> >
> > For bug reports, we can simply point to just kernel.org, as
> > this will reach my mchehab+samsung inbox anyway.  
> 
> I suppose this begs the question, why do we insist on adding our email
> addresses all over the place? On a quick grep, there are at least 40k+
> email addresses in the sources. Do we expect them all to be up-to-date
> too?

That's a good question.

The usual use case is that the e-mail allows people to contact developers
if needed. Such contact could simply due to something like handling SPDX
or other license-related issues or for troubleshooting.

There's also another reason (with IMHO, is more relevant): just the name
may not be enough to uniquely identify the author of some code. While
that might happen on occidental Countries, this is a way more relevant
for Asian Countries. For example, there are very few surnames on
some Countries there[1], and common names are usually... common. So, it
is not hard to find several people with exactly the same name working at
the same company. I've seen e-mails from those people that are things like
john.doe51@some.company, john.doe69@some.company, ...

[1] For example: https://en.wikipedia.org/wiki/List_of_Korean_surnames.

The e-mail is a way to uniquely identify a person. If we remove it,
then we may need to add another thing instead (like parents names,
security number or whatever), with would be weird, IMO. 

As we all use e-mails to uniquely identify contributors submissions,
IMHO, the best is to keep using e-mails. The side effect is that
we should keep those emails updated.

-

In the specific case of this patch, as I'm now just using @kernel.org
everywhere within the Kernel tree, I don't expect needing to change
it in long term.

Thanks,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-05-04 11:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 10:04 [PATCH] MAINTAINERS & files: Canonize the e-mails I use at files Mauro Carvalho Chehab
2018-05-04 10:58 ` Jani Nikula
2018-05-04 11:33   ` Mauro Carvalho Chehab [this message]
2018-05-09 12:57     ` Jan Kara

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=20180504083355.0c891ab3@vento.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=Julia.Lawall@lip6.fr \
    --cc=akpm@linux-foundation.org \
    --cc=arvind.yadav.cs@gmail.com \
    --cc=bhumirks@gmail.com \
    --cc=bparrot@ti.com \
    --cc=brad@nextdimension.cc \
    --cc=brian.warner@samsung.com \
    --cc=colin.king@canonical.com \
    --cc=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=davem@davemloft.net \
    --cc=dheitmueller@kernellabs.com \
    --cc=elfring@users.sourceforge.net \
    --cc=g.liakhovetski@gmx.de \
    --cc=garsilva@embeddedor.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=harryxiyou@gmail.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jack@suse.cz \
    --cc=jani.nikula@linux.intel.com \
    --cc=keescook@chromium.org \
    --cc=klimov.linux@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@zh-kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mawilcox@microsoft.com \
    --cc=mchehab@infradead.org \
    --cc=mchehab@s-opensource.com \
    --cc=n54@gmx.com \
    --cc=pombredanne@nexb.com \
    --cc=rdunlap@infradead.org \
    --cc=s.nawrocki@samsung.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sean@mess.org \
    --cc=tfiga@chromium.org \
    --cc=tharvey@gateworks.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=yamada.masahiro@socionext.com \
    --cc=yong.zhi@intel.com \
    /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).