From: Nick Terrell <terrelln@fb.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Zstd linux-next branches
Date: Fri, 19 Nov 2021 18:45:47 +0000 [thread overview]
Message-ID: <024447A0-35EE-4E8F-819A-675328A7A96C@fb.com> (raw)
Hi Stephen,
Would you please add these branches to linux-next:
git://github.com/terrelln/linux.git zstd-next
git://github.com/terrelln/linux.git zstd-linus
And remove this branch:
git://github.com/terrelln/linux.git zstd-1.4.10
As I’ve become more familiar with the linux workflow, I’ve
understood my mistake in naming the branch zstd-1.4.10.
I know that you pointed it out to me here:
> That sound good (or you could just call the branch zstd-next - unless
> this is a short term tree to just do the update and not ongoing work on
> zstd in the kernel?).
But, unfortunately I missed that email until after the zstd-1.4.10
branch was added. Sorry for adding more work for you!
Also, I think I’m asking for the right thing here, but if you think
what I’m asking for doesn’t make sense, please let me know!
Thanks,
Nick Terrell
next reply other threads:[~2021-11-19 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 18:45 Nick Terrell [this message]
2021-11-22 21:55 ` Zstd linux-next branches 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=024447A0-35EE-4E8F-819A-675328A7A96C@fb.com \
--to=terrelln@fb.com \
--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 NNTP newsgroup(s).