From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
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 18:22:29 +1000 [thread overview]
Message-ID: <20230710182229.36bcf79d@canb.auug.org.au> (raw)
In-Reply-To: <CANiq72npQiWMebvYTu8Z+XuJAyUH6-iygGtbF9V6y+R2aD1-vw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 628 bytes --]
Hi Miguel,
On Mon, 10 Jul 2023 11:11:08 +0200 Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
>
> On Mon, Jul 10, 2023 at 9:32 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > clang-format 2022-05-20 19:27:16 +0200
> > https://github.com/ojeda/linux.git clang-format
>
> We will eventually have updates for clang-format -- if it doesn't hurt
> too much keeping it, then I would prefer to have it around vs.
> creating it again later.
I have resurrected it. You might consider just resetting the branch to
something recent in Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-07-10 10:16 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 [this message]
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
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=20230710182229.36bcf79d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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=miguel.ojeda.sandonis@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=pablo@netfilter.org \
--cc=s.nawrocki@samsung.com \
--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 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).