From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Gabriel Krisman Bertazi <krisman@suse.de>
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: Tue, 11 Jul 2023 08:59:49 +1000 [thread overview]
Message-ID: <20230711085949.609305ef@canb.auug.org.au> (raw)
In-Reply-To: <87wmz7rej3.fsf@suse.de>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
Hi Gabriel,
On Mon, 10 Jul 2023 11:07:28 -0400 Gabriel Krisman Bertazi <krisman@suse.de> wrote:
>
> Stephen Rothwell <sfr@canb.auug.org.au> writes:
>
> > unicode 2022-04-28 18:19:09 -0400
> > git://git.kernel.org/pub/scm/linux/kernel/git/krisman/unicode.git for-next
> >
> > These branches are all empty except the last which just contains a
> > commit that is the same patch of a commit in Linus' tree.
>
> Please, keep it. It is not a busy area for development, but we I'm
> looking into a unicode version update soon that will go through
> this tree.
I have added it back. You might consider rebasing it onto v6.5-rc1 and
I think you will find that its only commit will disappear.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-07-10 23:00 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
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 [this message]
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=20230711085949.609305ef@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dhowells@redhat.com \
--cc=krisman@collabora.com \
--cc=krisman@suse.de \
--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=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