From: Kent Overstreet <kent.overstreet@linux.dev>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] More bcachefs updates for 6.8-rc1
Date: Sun, 21 Jan 2024 17:42:44 -0500 [thread overview]
Message-ID: <ianqurcjmgjvciii3k4dxr5bwargskiwspnfzzy4dqhbn2sdgp@r3v2ysfo5dqq> (raw)
In-Reply-To: <CAHk-=wjKjvytH19t2mMHZbkY2bpGurGbG4Tb7xmTjfzA71Lb7g@mail.gmail.com>
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@linux.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?
next prev parent reply other threads:[~2024-01-21 22:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 21:35 [GIT PULL] More bcachefs updates for 6.8-rc1 Kent Overstreet
2024-01-21 22:05 ` Linus Torvalds
2024-01-21 22:42 ` Kent Overstreet [this message]
2024-01-21 22:23 ` 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=ianqurcjmgjvciii3k4dxr5bwargskiwspnfzzy4dqhbn2sdgp@r3v2ysfo5dqq \
--to=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 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).