From: J Lovejoy <opensource@jilayne.com>
To: Allison Randal <allison@lohutok.net>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-spdx@vger.kernel.org
Subject: Re: [patch 0/4] SPDX: First batch of patches
Date: Wed, 8 May 2019 15:36:23 -0600 [thread overview]
Message-ID: <C57577B3-5C81-4C7D-98D2-FA490EFDD521@jilayne.com> (raw)
In-Reply-To: <3b787618-1f40-4195-b760-f3d48b37a766@lohutok.net>
> On May 8, 2019, at 3:33 PM, Allison Randal <allison@lohutok.net> wrote:
>
> On 5/8/19 10:29 PM, Thomas Gleixner wrote:
>> On Wed, 8 May 2019, Allison Randal wrote:
>>> On 5/8/19 9:23 PM, Thomas Gleixner wrote:
>>>
>>> Though, maybe it would be better if I said nothing and allowed the whole
>>> idea to be forgotten...
>>
>> Ahhh that one. That's an easy to do add on if people insist ....
>
> Shhhhhh, if we're very quiet, maybe they won’t…
>
I’ll have a think on this and chat with Mike Dolan to follow-up on our discussions in Barcelona on this one.
Thomas - would I be correct to assume that having the answer to this sooner-than-later, so this can begin being compiled would be helpful, or it is not make much difference as to timing?
Thanks,
Jilayne
next prev parent reply other threads:[~2019-05-08 22:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 12:19 [patch 0/4] SPDX: First batch of patches Thomas Gleixner
2019-05-07 12:19 ` [patch 2/4] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 2 Thomas Gleixner
2019-05-07 12:19 ` [patch 3/4] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 3 Thomas Gleixner
2019-05-07 12:19 ` [patch 4/4] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 4 Thomas Gleixner
2019-05-07 13:59 ` [patch 0/4] SPDX: First batch of patches Thomas Gleixner
2019-05-07 14:03 ` [patch 1/4] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 1 Thomas Gleixner
2019-05-07 14:17 ` [patch 0/4] SPDX: First batch of patches Greg KH
2019-05-07 14:19 ` Thomas Gleixner
2019-05-07 18:14 ` Greg KH
2019-05-07 18:43 ` Thomas Gleixner
2019-05-07 18:58 ` Greg KH
2019-05-08 6:25 ` Thomas Gleixner
2019-05-08 6:46 ` Greg KH
2019-05-08 9:26 ` Thomas Gleixner
2019-05-08 9:51 ` Greg KH
2019-05-08 10:09 ` Greg KH
2019-05-08 20:40 ` Thomas Gleixner
2019-05-08 17:29 ` Allison Randal
2019-05-08 20:23 ` Thomas Gleixner
2019-05-08 21:25 ` Allison Randal
2019-05-08 21:29 ` Thomas Gleixner
2019-05-08 21:33 ` Allison Randal
2019-05-08 21:36 ` J Lovejoy [this message]
2019-05-08 21:58 ` Thomas Gleixner
2019-05-09 4:04 ` J Lovejoy
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=C57577B3-5C81-4C7D-98D2-FA490EFDD521@jilayne.com \
--to=opensource@jilayne.com \
--cc=allison@lohutok.net \
--cc=linux-spdx@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).