From: Eric Van Hensbergen <ericvh@kernel.org>
To: sfr@canb.auug.org.au
Cc: v9fs-developer@lists.sourceforge.net, linux-next@vger.kernel.org
Subject: Add v9fs#fixes/next branch to linux-next pending-fixes
Date: Mon, 27 Mar 2023 01:06:49 +0000 [thread overview]
Message-ID: <ZCDsKfJ9fU6cwiZM@7e9e31583646> (raw)
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
Could we get the fixes/next branch of my v9fs tree
(https://git.kernel.org/pub/scm/linux/kernel/git/ericvh/v9fs.git/log/?h=fixes/next)
added to linux-next pending-fixes branch? Intent is to use that for
pending fixes that are reviewed, tested, and signed-off but intend to
send to Linus before the next merge window. I'll continue to use
ericvh/for-next for features that are intended for the next merge
window.
Thanks,
- eric
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-03-27 1:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 1:06 Eric Van Hensbergen [this message]
2023-03-27 1:48 ` Add v9fs#fixes/next branch to linux-next pending-fixes 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=ZCDsKfJ9fU6cwiZM@7e9e31583646 \
--to=ericvh@kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=v9fs-developer@lists.sourceforge.net \
/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