From: "Theodore Ts'o" <tytso@mit.edu>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Legal question: Author, Sign-off, Company Copyright and gmail
Date: Thu, 9 Nov 2017 11:29:34 -0500 [thread overview]
Message-ID: <20171109162934.coyrbprbjitllm3r@thunk.org> (raw)
In-Reply-To: <084f9151-523e-a212-bf27-d4a4c23878e4@linaro.org>
On Thu, Nov 09, 2017 at 10:45:27AM +0100, Daniel Lezcano wrote:
>
> Hi all,
>
> I noticed a practice when the patches are submitted where I'm a bit
> confused about how it fits with the DCO.
>
> People are creating gmail accounts to send patches on behalf of their
> company because the company's email configuration does not allow to send
> patches or adds extra infos, or whatever...
>
> That ends up with patches submitted by a gmail account with no history
> and verifiable origin and new files containing a company copyright [1].
>
> At the first glance I would say, it is not allowed, and if a company is
> willing to do opensource, it should provide the tools to its employees
> to do so. But I don't want block patch submission if this practice is
> tolerated.
Note that git send-email will automatically take care of this case by
taking the From field from the author field of git, and moving it into
the body. So you might have an e-mail message which looks like this:
From: <user.lastname>@gmail.com
Subject: [PATCH] some patch
Date: April 1, 2017
Other-mail-headers: etc. etc.
From: User Lastname <luser@company.with.busted.exchange.server.net>
This is some patch!
...
And then git apply-patch will automatically use the first From field
in the "pseudo-header" instead of the From field in the mail header.
Other people will do this because they they have a username@kernel.org
account, and they want all of their Kernel git commits to have
username@kernel.org in the author field, so they'll do the same thing
of putting "From: username@kernel.org" as the first line of the body
--- either manually, or by setting the appropriate git configuration
variables so that username@kernel.org gets used as the author
information in the git commit.
So what e-mail you use when you interact with the kernel mailing
lists, what e-mail address you want to show up in the git commit's
author field, and which company should get credit for your
contributions for a given period of time in the Linux Foundation's
"who writes Linux" report are three separable issues.
You could be using gmail.com for patch submission, use your kernel.org
address for git author fields, while working for nokia.com. And
that's just fine.
Cheers,
- Ted
prev parent reply other threads:[~2017-11-09 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 9:45 Daniel Lezcano
2017-11-09 10:44 ` Greg Kroah-Hartman
2017-11-09 11:19 ` Daniel Lezcano
2017-11-09 16:29 ` Theodore Ts'o [this message]
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=20171109162934.coyrbprbjitllm3r@thunk.org \
--to=tytso@mit.edu \
--cc=daniel.lezcano@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome