linux-kernel - Re: [GIT PULL] More bcachefs updates for 6.8-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ianqurcjmgjvciii3k4dxr5bwargskiwspnfzzy4dqhbn2sdgp@r3v2ysfo5dqq>
Date: Sun, 21 Jan 2024 17:42:44 -0500
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: linux-bcachefs@...r.kernel.org, linux-fsdevel@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] More bcachefs updates for 6.8-rc1

On Sun, Jan 21, 2024 at 02:05:55PM -0800, Linus Torvalds wrote:
> On Sun, 21 Jan 2024 at 13:35, Kent Overstreet <kent.overstreet@...ux.dev> wrote:
> >
> > Hi Linus, another small bcachefs pull. Some fixes, Some refactoring,
> > some minor features.
> 
> I'm taking this, but only because bcachefs is new.
> 
> You need to be aware that the merge window is for *merging*. Not for
> new development.
> 
> And almost all of the code here is new development.
> 
> What you send during the merge window is stuff that should all have
> been ready *before* the merge window opened, not whatever random
> changes you made during it.
> 
> Now, fixes happen any time, but for that argument to work they need to
> be real fixes. Not "reorganize the code to make things easier to fix"
> with the fix being something small on top of a big change.

I thought the merge window was still open until tonight?