From: Allison Randal <allison@lohutok.net>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-spdx@vger.kernel.org
Subject: Re: Workflow
Date: Fri, 10 May 2019 12:02:58 +0100 [thread overview]
Message-ID: <9e059771-89e0-3cd7-0ae0-74699d6f0b5a@lohutok.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1905101252350.1751@nanos.tec.linutronix.de>
On 5/10/19 11:54 AM, Thomas Gleixner wrote:
>
> I'm keeping the first few file diffs in the mail anyway, I just need to
> cutoff for the larger patches to avoid the size limit of the list. The URL
> is there for reference and for those who really want to look at every
> change :)
Makes sense. That'll be perfect for me. :)
Allison
next prev parent reply other threads:[~2019-05-10 11:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 14:11 Workflow Thomas Gleixner
2019-05-09 14:45 ` Workflow Kate Stewart
2019-05-09 21:56 ` Workflow Thomas Gleixner
2019-05-10 9:25 ` Workflow Allison Randal
2019-05-10 10:54 ` Workflow Thomas Gleixner
2019-05-10 11:02 ` Allison Randal [this message]
2019-05-10 13:01 ` Workflow Kate Stewart
2019-05-10 13:18 ` Workflow Bradley M. Kuhn
2019-05-10 9:06 ` Workflow Greg KH
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=9e059771-89e0-3cd7-0ae0-74699d6f0b5a@lohutok.net \
--to=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).