From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Carlos Maiolino <cem@kernel.org>,
linux-xfs@vger.kernel.org, david@fromorbit.com,
sandeen@redhat.com, bfoster@redhat.com, aalbersh@kernel.org,
axboe@kernel.dk
Subject: Re: Changes to XFS patch integration process
Date: Mon, 10 Mar 2025 11:36:42 +0100 [thread overview]
Message-ID: <20250310103642.GA4378@lst.de> (raw)
In-Reply-To: <20250306174012.GN2803749@frogsfrogsfrogs>
On Thu, Mar 06, 2025 at 09:40:12AM -0800, Darrick J. Wong wrote:
> Eliminating the possibility of such messes is also why I avoided doing
> bugfixes and merge window prep whenever I could. ;)
Thats a good idea in general, but xfs took it a bit too far. We really
should hae had major changes in linux-next for a ew weeks and not in the
last minute.
prev parent reply other threads:[~2025-03-10 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 10:42 Changes to XFS patch integration process Carlos Maiolino
2025-03-03 14:05 ` Christoph Hellwig
2025-03-03 15:00 ` Carlos Maiolino
2025-03-03 15:24 ` Christoph Hellwig
2025-03-04 20:20 ` Darrick J. Wong
2025-03-06 7:50 ` Carlos Maiolino
2025-03-06 17:08 ` Christoph Hellwig
2025-03-06 17:40 ` Darrick J. Wong
2025-03-10 10:36 ` Christoph Hellwig [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=20250310103642.GA4378@lst.de \
--to=hch@lst.de \
--cc=aalbersh@kernel.org \
--cc=axboe@kernel.dk \
--cc=bfoster@redhat.com \
--cc=cem@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.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