From: Florian Westphal <fw@strlen.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
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 09:46:56 +0200 [thread overview]
Message-ID: <20230710074656.GA32562@breakpoint.cc> (raw)
In-Reply-To: <20230710172602.05d32c03@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> netfilter 2022-05-23 14:33:38 -0700
> git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf.git master
The tree changed to
git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git main
> netfilter-next 2022-05-23 21:19:17 -0700
> git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git master
This changed to
git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf-next.git main
next prev parent reply other threads:[~2023-07-10 7:47 UTC|newest]
Thread overview: 12+ 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 [this message]
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
2023-07-10 23:04 ` Stephen Rothwell
2023-07-12 3:58 ` Vignesh Raghavendra
2023-07-12 4:44 ` 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=20230710074656.GA32562@breakpoint.cc \
--to=fw@strlen.de \
--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=vgupta@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.