public inbox for smatch@vger.kernel.org
 help / color / mirror / Atom feed
From: John Levon <levon@movementarian.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
	Dan Carpenter <dan.carpenter@oracle.com>
Cc: smatch@vger.kernel.org
Subject: Re: [PATCH 05/18] sparse: correctly handle "-D foo" and "-U foo". The former is from sparse upstream, but they didn't fix the latter for some reason.
Date: Mon, 26 Nov 2018 08:44:36 +0000	[thread overview]
Message-ID: <20181126084436.GC10025@movementarian.org> (raw)
In-Reply-To: <20181126074909.GI2970@unbuntlaptop> <20181126002734.rmk5kmvtjtol2m2h@ltop.local>

On Mon, Nov 26, 2018 at 01:27:35AM +0100, Luc Van Oostenryck wrote:

> Putting this DCO question aside, I would find normal that the commit
> message would contains a small note adding something like:
>       [This patch was originally written by ...]

It's in the subject (where it ended up from git format-patch). Dan has
already taken me to task for the format of the commits here.

> The signed-off-by should be like:
>       Signed-off-by: Original Author <author@example.com>
>       Signed-off-by: John Levon <levon@movementarian.org>

This sounds awfully like *you've* signed off on *this* patch, but sure,
whatever is the usual way.

On Mon, Nov 26, 2018 at 10:49:09AM +0300, Dan Carpenter wrote:

> It looks like everything was BCC instead of To: and Cc:?  I can't tell
> which went to linux-sparse and which smatch@vger.kernel.org.  Smatch is
> GPL and Sparse is MIT, but any shared code is MIT licensed.

I screwed up the mailing (next ones will be better), but they all went
to smatch. As being in smatch and not sparse is of no use to us, I
thought this made sense right now at least until smatch is nearer
upstream.

> cherry-pick those two patches.  Or John, you could cherry-pick them and
> send them to me.  `man git cherry-pick`.

There's a good few more than just two. If you'd prefer, I can work on
taking them upstream first?

regards
john

  parent reply	other threads:[~2018-11-26 19:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22 12:08 [PATCH 05/18] sparse: correctly handle "-D foo" and "-U foo". The former is from sparse upstream, but they didn't fix the latter for some reason John Levon
2018-11-25 21:29 ` Luc Van Oostenryck
2018-11-25 23:29   ` John Levon
2018-11-26  0:27     ` Luc Van Oostenryck
2018-11-26  7:49       ` Dan Carpenter
2018-11-29 10:03         ` Sync smatch with sparse? Luc Van Oostenryck
2018-11-29 10:09           ` John Levon
2018-11-26  8:44       ` John Levon [this message]
2018-11-26  9:18         ` [PATCH 05/18] sparse: correctly handle "-D foo" and "-U foo". The former is from sparse upstream, but they didn't fix the latter for some reason Dan Carpenter

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=20181126084436.GC10025@movementarian.org \
    --to=levon@movementarian.org \
    --cc=dan.carpenter@oracle.com \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=smatch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox