From: Tyler Hicks <code@tyhicks.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
ecryptfs@vger.kernel.org, brauner@kernel.org
Subject: linux-next: Please re-add eCryptfs next branch
Date: Mon, 21 Oct 2024 01:58:26 -0500 [thread overview]
Message-ID: <ZxX7khzjUaDOpfOt@redbud> (raw)
Hi Stephen - Earlier this year, you dropped the eCryptfs next branch due
to inactivity. I'd like to request that you re-add it back now as there
are some patches piling up to bring eCryptfs up-to-date with the new
mount API, folios, and a few other trivial cleanups.
git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git#next
Thank you!
Tyler
next reply other threads:[~2024-10-21 6:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 6:58 Tyler Hicks [this message]
2024-10-21 7:23 ` linux-next: Please re-add eCryptfs next branch Stephen Rothwell
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=ZxX7khzjUaDOpfOt@redbud \
--to=code@tyhicks.com \
--cc=brauner@kernel.org \
--cc=ecryptfs@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).