All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: Jani Partanen <jiipee@sotapeli.fi>,
	Kent Overstreet <kent.overstreet@linux.dev>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.16-rc3
Date: Fri, 20 Jun 2025 09:27:59 +0200	[thread overview]
Message-ID: <2793428.mvXUDI8C0e@lichtvoll.de> (raw)
In-Reply-To: <3366564.44csPzL39Z@lichtvoll.de>

Martin Steigerwald - 20.06.25, 09:12:21 CEST:
> If you stick to your approach about merge window rules and many other
> kernel developers including Linus stick to their rules this will go in
> circles.
> 
> Indefinitely so.

Also it has even been quite predictable.

The moment I saw your merge request I would have been very surprised if 
Linus would just have pulled it.

-- 
Martin



  reply	other threads:[~2025-06-20  7:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 23:06 [GIT PULL] bcachefs fixes for 6.16-rc3 Kent Overstreet
2025-06-20  0:51 ` Linus Torvalds
2025-06-20  1:09   ` Kent Overstreet
2025-06-20  1:25     ` Jani Partanen
2025-06-20  1:51       ` Kent Overstreet
2025-06-20  7:12         ` Martin Steigerwald
2025-06-20  7:27           ` Martin Steigerwald [this message]
2025-06-20  8:14           ` Kent Overstreet
2025-06-20 12:43             ` Theodore Ts'o
2025-06-20 15:17               ` Christoph Heinrich
2025-06-20 23:34               ` Kent Overstreet
2025-06-21  0:15                 ` Kent Overstreet
2025-06-21 21:07                   ` Jérôme Poulin
2025-06-21 22:50                     ` Jérôme Poulin
2025-06-21 23:46                     ` Kent Overstreet
2025-06-27  3:33 ` pr-tracker-bot

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=2793428.mvXUDI8C0e@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=jiipee@sotapeli.fi \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.