From: Vineet Gupta <vgupta@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
Gabriel Krisman Bertazi <krisman@collabora.com>,
Leo Li <leoyang.li@nxp.com>, Lucas Stach <l.stach@pengutronix.de>,
Miguel Ojeda <ojeda@kernel.org>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Vineet Gupta <vgupta@kernel.org>,
NetFilter <netfilter-devel@vger.kernel.org>
Subject: Re: linux-next: branches to be removed
Date: Mon, 10 Jul 2023 10:52:08 -0700 [thread overview]
Message-ID: <ccc0f8d4-3900-a766-7303-85e44bffd875@kernel.org> (raw)
In-Reply-To: <20230710172602.05d32c03@canb.auug.org.au>
Hi Stephen,
On 7/10/23 00:26, Stephen Rothwell wrote:
> Hi all,
>
> I will remove the following branches from linux-next tomorrow as they have
> not been updated in over a year. If you want your branch retained or
> reinstated, please just send me an email letting me know.
>
> Tree Last commit date
> ---- ----------------
> arc 2022-06-05 17:18:54 -0700
> git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git for-next
Would request to please keep arc next around even though upstream dev is
slow'ish these days.
I do have some patches for absolute near future as well.
Thx,
-Vineet
next prev parent reply other threads:[~2023-07-10 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 7:26 linux-next: branches to be removed Stephen Rothwell
2023-07-10 7:46 ` Florian Westphal
2023-07-10 8:40 ` Stephen Rothwell
2023-07-10 9:11 ` Miguel Ojeda
2023-07-10 8:22 ` Stephen Rothwell
2023-07-10 10:41 ` Miguel Ojeda
2023-07-10 15:07 ` Gabriel Krisman Bertazi
2023-07-10 22:59 ` Stephen Rothwell
2023-07-10 17:52 ` Vineet Gupta [this message]
2023-07-10 23:04 ` 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=ccc0f8d4-3900-a766-7303-85e44bffd875@kernel.org \
--to=vgupta@kernel.org \
--cc=dhowells@redhat.com \
--cc=krisman@collabora.com \
--cc=l.stach@pengutronix.de \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=pablo@netfilter.org \
--cc=s.nawrocki@samsung.com \
--cc=sfr@canb.auug.org.au \
--cc=vigneshr@ti.com \
/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).