From: "Theodore Ts'o" <tytso@mit.edu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Tue, 7 Mar 2023 19:45:42 -0500 [thread overview]
Message-ID: <20230308004542.GA1867364@mit.edu> (raw)
In-Reply-To: <20230308074431.21c32d58@oak.ozlabs.ibm.com>
On Wed, Mar 08, 2023 at 07:45:13AM +1100, Stephen Rothwell wrote:
>
> 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.
Ah, sorry. I had pushed the tag, but not the branch. My bad. Anyway, fixed.
- Ted
next prev parent reply other threads:[~2023-03-08 0:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 23:24 Linux 6.3-rc1 Linus Torvalds
2023-03-06 1:41 ` linux-next: stats (Was: Linux 6.3-rc1) Stephen Rothwell
2023-03-06 3:17 ` The state of ext4 tree merging (was " 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
2023-03-08 0:45 ` Theodore Ts'o [this message]
2023-03-06 8:20 ` Build regressions/improvements in v6.3-rc1 Geert Uytterhoeven
2023-03-06 8:42 ` Geert Uytterhoeven
2023-03-06 8:42 ` Geert Uytterhoeven
2023-03-06 8:42 ` Geert Uytterhoeven
2023-03-06 16:52 ` Linux 6.3-rc1 Guenter Roeck
2023-03-06 18:12 ` Linus Torvalds
2023-03-06 22:02 ` Guenter Roeck
2023-03-08 10:07 ` Luna Jernberg
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=20230308004542.GA1867364@mit.edu \
--to=tytso@mit.edu \
--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=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--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 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.