public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chandan Babu R <chandanbabu@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: helpdesk@kernel.org, Theodore Ts'o <tytso@mit.edu>,
	xfs <linux-xfs@vger.kernel.org>,
	Catherine Hoang <catherine.hoang@oracle.com>,
	Leah Rumancik <lrumancik@google.com>,
	Carlos Maiolino <cem@kernel.org>,
	Amir Goldstein <amir73il@gmail.com>
Subject: Re: Create xfs-stable@lists.linux.dev
Date: Fri, 20 Dec 2024 18:56:43 +0530	[thread overview]
Message-ID: <87msgqiin6.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <20241219183237.GF6197@frogsfrogsfrogs>

On Thu, Dec 19, 2024 at 10:32:37 AM -0800, Darrick J. Wong wrote:
> Hi there,
>
> Could we create a separate mailing list to coordinate XFS LTS
> stable backporting work?  There's enough traffic on the main XFS list
> that the LTS backports get lost in the noise, and in the future we'd
> like to have a place for our LTS testing robots to send automated email.
>
> A large portion of the upstream xfs community do not participate in LTS
> work so there's no reason to blast them with all that traffic.  What do
> the rest of you think about this?
>

I would welcome this suggestion. It helps stake holders interested in "XFS in
LTS kernels" to quickly get an overview of the issues and current progress
made on LTS kernels.

-- 
Chandan

  reply	other threads:[~2024-12-20 13:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 18:32 Create xfs-stable@lists.linux.dev Darrick J. Wong
2024-12-20 13:26 ` Chandan Babu R [this message]
2024-12-20 15:47 ` Eric Sandeen
2024-12-20 18:37 ` Konstantin Ryabitsev
2025-01-06 19:21   ` Leah Rumancik

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=87msgqiin6.fsf@debian-BULLSEYE-live-builder-AMD64 \
    --to=chandanbabu@kernel.org \
    --cc=amir73il@gmail.com \
    --cc=catherine.hoang@oracle.com \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=helpdesk@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lrumancik@google.com \
    --cc=tytso@mit.edu \
    /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