linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.11-rc5
Date: Sat, 24 Aug 2024 10:35:38 +0800	[thread overview]
Message-ID: <CAHk-=wgpb0UPYYSe6or8_NHKQD+VooTxpfgSpHwKydhm3GkS0A@mail.gmail.com> (raw)
In-Reply-To: <nxyp62x2ruommzyebdwincu26kmi7opqq53hbdv53hgqa7zsvp@dcveluxhuxsd>

On Sat, 24 Aug 2024 at 10:33, Kent Overstreet <kent.overstreet@linux.dev> wrote:
>
> What is to be gained by holding back fixes, if we've got every reason to
> believe that the fixes are solid?

What is to be gained by having release rules and a stable development
environment? I wonder.

            Linus

  reply	other threads:[~2024-08-24  2:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-23 18:54 [GIT PULL] bcachefs fixes for 6.11-rc5 Kent Overstreet
2024-08-24  1:23 ` Linus Torvalds
2024-08-24  2:13   ` Kent Overstreet
2024-08-24  2:25     ` Linus Torvalds
2024-08-24  2:33       ` Kent Overstreet
2024-08-24  2:35         ` Linus Torvalds [this message]
2024-08-24  2:40           ` Linus Torvalds
2024-08-24  2:59             ` Kent Overstreet
2024-08-24  4:22               ` Carl E. Thompson
2024-08-24 11:48                 ` Kent Overstreet
2024-08-24  2:47           ` Kent Overstreet
2024-08-24  2:57             ` Linus Torvalds
2024-08-24  3:10               ` Kent Overstreet
  -- strict thread matches above, loose matches on Subject: below --
2024-09-06  7:50 Nathan Owens

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='CAHk-=wgpb0UPYYSe6or8_NHKQD+VooTxpfgSpHwKydhm3GkS0A@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).