From: Chris Li <christ.li@gmail.com>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] cgcc: teach cgcc about GNU/kFreeBSD
Date: Wed, 20 Sep 2017 00:45:51 -0400 [thread overview]
Message-ID: <CANeU7Q=TMSjqUkVsA05NQvpyQpUwhYsFqXRCUbkn1+aMqJe=Sg@mail.gmail.com> (raw)
In-Reply-To: <b580c0f7-716d-17b0-7e2b-410530c4a0cf@kleine-koenig.org>
On Tue, Sep 19, 2017 at 1:33 PM, Uwe Kleine-König <uwe@kleine-koenig.org> wrote:
>> It did in sparse Documentation/submitting-patches.md.
>
> ah, I missed that. (I wonder if it is sensible to just link to the
> respective kernel stuff instead of copying that verbatim into sparse,
> but I don't really care.)
Maybe. The kernel is GPL and sparse is MIT licensed.
If I copy the text, I need to make special case for the license of
that document under GPL. It is doable that way as well.
I just take the lazy route link to the kernel documents.
> I can resend accordingly
Send just the SOB line is good enough. You don't have to
re-create the patch.
Chris
next prev parent reply other threads:[~2017-09-20 4:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 20:03 [PATCH] cgcc: teach cgcc about GNU/kFreeBSD Uwe Kleine-König
2017-09-14 20:17 ` Uwe Kleine-König
2017-09-15 5:09 ` Luc Van Oostenryck
2017-09-15 4:50 ` Luc Van Oostenryck
2017-09-15 16:56 ` Chris Li
2017-09-16 7:50 ` Luc Van Oostenryck
2017-09-16 13:57 ` Uwe Kleine-König
2017-09-19 12:25 ` Chris Li
2017-09-19 14:41 ` Uwe Kleine-König
2017-09-19 15:15 ` Chris Li
2017-09-19 17:33 ` Uwe Kleine-König
2017-09-20 4:45 ` Chris Li [this message]
2017-09-20 15:10 ` [PATCH v2] " Uwe Kleine-König
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='CANeU7Q=TMSjqUkVsA05NQvpyQpUwhYsFqXRCUbkn1+aMqJe=Sg@mail.gmail.com' \
--to=christ.li@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=uwe@kleine-koenig.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;
as well as URLs for NNTP newsgroup(s).