From: Matthias Goergens <matthias.goergens@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jirislaby@kernel.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: name the gregkh/tty tty-next branch
Date: Thu, 1 Oct 2026 19:25:22 +0800 [thread overview]
Message-ID: <20261001112522.3822619-1-matthias.goergens@gmail.com> (raw)
In-Reply-To: <2026092800-clustered-unlighted-a54a@gregkh>
Hi Greg,
> Hint, -linus is for bugfixes "now" and -next is for the next release.
> So why pick just one for this entry? 50% of the chance of getting it
> right?
Fair point: one branch cannot describe a tree with both, so please drop
this one, and sorry for the noise.
The motivation was Sashiko, which used to review against the default
branch of the tree in T:. Since 28 September it skips a default branch
that mainline already contains and uses linux-next instead, which has
both tty-linus and tty-next. That makes the patch unnecessary.
Thanks,
Matthias
prev parent reply other threads:[~2026-10-01 11:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 10:59 [PATCH] MAINTAINERS: name the gregkh/tty tty-next branch Matthias Goergens
2026-09-28 11:44 ` Greg Kroah-Hartman
2026-10-01 11:25 ` Matthias Goergens [this message]
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=20261001112522.3822619-1-matthias.goergens@gmail.com \
--to=matthias.goergens@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/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