From: Dan Carpenter <dan.carpenter@oracle.com>
To: George Spelvin <lkml@SDF.ORG>
Cc: devel@driverdev.osuosl.org, Ajay.Kathat@microchip.com,
gregkh@linuxfoundation.org, linux-wireless@vger.kernel.org,
Adham.Abozaeid@microchip.com, johannes@sipsolutions.net
Subject: Re: [PATCH v3] staging: wilc1000: Use crc7 in lib/ rather than a private copy
Date: Sat, 4 Apr 2020 20:25:37 +0300 [thread overview]
Message-ID: <20200404172537.GI2066@kadam> (raw)
In-Reply-To: <20200403234028.GA11944@SDF.ORG>
On Fri, Apr 03, 2020 at 11:40:28PM +0000, George Spelvin wrote:
> I understand that it's addressed more to patch authors than
> maintainers forwarding them, but I've read that thing a dozen times,
> and the description of S-o-b always seemed to be about copyright.
>
It's to say that you didn't add anything which you shouldn't have, for
example, secret SCO UnixWare stuff.
> So I had assumed that edits which were below the de minimus standard
> of copyright didn't need a separate S-o-b.
>
> Am I right that there should be an S-o-b from everyone from the
> patch author to the patch committer (as recorded in git)? And the
> one exception is that we don't need S-o-b for git pulls after that,
> because the merge commits record the information?
Yes. Also if people added their S-o-b for git merges it would change
the git hash for the patch which would suck.
regards,
dan carpenter
next prev parent reply other threads:[~2020-04-04 17:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 15:23 [PATCH v3] staging: wilc1000: Use crc7 in lib/ rather than a private copy Ajay.Kathat
2020-04-02 8:27 ` Dan Carpenter
2020-04-02 13:36 ` Ajay.Kathat
2020-04-02 15:30 ` George Spelvin
2020-04-03 9:10 ` Dan Carpenter
2020-04-03 23:40 ` George Spelvin
2020-04-04 10:05 ` Kalle Valo
2020-04-04 17:25 ` Dan Carpenter [this message]
2020-04-04 18:15 ` George Spelvin
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=20200404172537.GI2066@kadam \
--to=dan.carpenter@oracle.com \
--cc=Adham.Abozaeid@microchip.com \
--cc=Ajay.Kathat@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=lkml@SDF.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.