From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>, Bagas Sanjaya <bagasdotme@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
ext4 Development <linux-ext4@vger.kernel.org>
Subject: Re: The state of ext4 tree merging (was Re: Linux 6.3-rc1)
Date: Wed, 8 Mar 2023 07:45:13 +1100 [thread overview]
Message-ID: <20230308074431.21c32d58@oak.ozlabs.ibm.com> (raw)
In-Reply-To: <20230307162137.GB960946@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
Hi Theodore,
On Tue, 7 Mar 2023 11:21:37 -0500 "Theodore Ts'o" <tytso@mit.edu> wrote:
>
> What duplicate commits? As far as I know there aren't any. My normal
> practice is to send a secondary push to fix a few bug fixes targetted
> for upcoming release (in this case, 6.3), and then I'll reset to -rc2
> or -rc3 for patches that are targetted for the next merge window (in
> this case, 6.4).
>
> The data=writeback patches was dropped from dev before the pull
> request, and won't show up on dev until they are ready for Linus.
Did you forget to push the dev branch out? The version I have (and still see on git.kernel.org) has commit
2c2dec1e86cc ("ext4: fix incorrect options show of original mount_opt and extend mount_opt2")
at its head, but what you sent to Linus has commit
e3645d72f886 ("ext4: fix incorrect options show of original mount_opt and extend mount_opt2")
at its head.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-03-07 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHk-=wgr1D8hb75Z+nn+4LXUnosp0HM+gP+YJEcEav1DgTC=Cw@mail.gmail.com>
2023-03-06 3:17 ` The state of ext4 tree merging (was Re: Linux 6.3-rc1) Bagas Sanjaya
2023-03-06 12:41 ` Jan Kara
2023-03-06 22:02 ` Stephen Rothwell
2023-03-07 16:21 ` Theodore Ts'o
2023-03-07 20:45 ` Stephen Rothwell [this message]
2023-03-08 0:45 ` Theodore Ts'o
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=20230308074431.21c32d58@oak.ozlabs.ibm.com \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=willy@infradead.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).