From: "Chris Hoy Poy via RT" <kernel-helpdesk@rt.linuxfoundation.org>
To: ebiggers@kernel.org
Cc: linux-fscrypt@vger.kernel.org
Subject: [Kernel.org Helpdesk #80522] Please add linux-fscrypt@vger.kernel.org to lore.kernel.org
Date: Wed, 23 Oct 2019 03:37:41 -0400 [thread overview]
Message-ID: <rt-4.4.0-17358-1571816261-967.80522-6-0@linuxfoundation> (raw)
In-Reply-To: <rt-4.4.0-17361-1571711745-65.80522-6-0@linuxfoundation>
Hi Eric,
cheers - this is complete and accessible at
https://lore.kernel.org/linux-fscrypt/
Let me know if you have any issues
cheers
/Chris
On Tue Oct 22 10:35:45 2019, ebiggers@kernel.org wrote:
> On Mon, Oct 21, 2019 at 01:15:01AM -0400, Chris Hoy Poy via RT wrote:
> > Hi Eric,
> >
> > I've subscribed lore for new emails to linux-fscrypt - if you can
> > provide an archive (there are no obvious ones I can find), I can
> > import that for history.
> >
> > cheers
> > /Chris
> >
> > On Wed Oct 16 09:08:18 2019, ebiggers@kernel.org wrote:
> > > Hi, could you please start archiving the linux-fscrypt mailing list
> > > at
> > > lore.kernel.org?
> > >
> > > I can provide an archive which should be complete --- I've been
> > > subscribed to
> > > the list from the beginning.
> > >
> > > Thanks!
> > >
> > > - Eric
> >
> >
>
> I've attached my archive.
>
> - Eric
--
Chris Hoy Poy
Collaborative Projects IT
The Linux Foundation
prev parent reply other threads:[~2019-10-23 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-80522@linuxfoundation>
2019-10-16 1:08 ` Please add linux-fscrypt@vger.kernel.org to lore.kernel.org Eric Biggers
2019-10-21 5:15 ` [Kernel.org Helpdesk #80522] " Chris Hoy Poy via RT
2019-10-21 5:15 ` Chris Hoy Poy via RT
[not found] ` <20191022023537.GB938@sol.localdomain>
[not found] ` <rt-4.4.0-17361-1571711745-65.80522-6-0@linuxfoundation>
2019-10-23 7:37 ` Chris Hoy Poy via RT [this message]
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=rt-4.4.0-17358-1571816261-967.80522-6-0@linuxfoundation \
--to=kernel-helpdesk@rt.linuxfoundation.org \
--cc=ebiggers@kernel.org \
--cc=linux-fscrypt@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