From: Randy Dunlap <rdunlap@infradead.org>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
ksummit-discuss@lists.linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, workflows@vger.kernel.org
Subject: Re: New list for people to share maintainer workflows
Date: Fri, 13 Sep 2019 08:04:07 -0700 [thread overview]
Message-ID: <29b46dfe-173b-7022-8676-f3c4000a8375@infradead.org> (raw)
In-Reply-To: <20190913073849.GA15965@mit.edu>
On 9/13/19 12:38 AM, Theodore Y. Ts'o wrote:
> Let's continue the discussion on workflows@vger.kernel.org.
Hi,
Will this be archived on lore.kernel.org?
thnx.
--
~Randy
next prev parent reply other threads:[~2019-09-13 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 7:38 Theodore Y. Ts'o
2019-09-13 15:04 ` Randy Dunlap [this message]
2019-09-13 15:09 ` [Ksummit-discuss] " Greg KH
2019-09-14 16:45 ` Drew DeVault
2019-09-24 9:26 ` Paolo Bonzini
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=29b46dfe-173b-7022-8676-f3c4000a8375@infradead.org \
--to=rdunlap@infradead.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=workflows@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