From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: patches in queue but missing from series?
Date: Sun, 14 Sep 2008 14:11:08 -0700 [thread overview]
Message-ID: <48CD7DEC.6080008@redhat.com> (raw)
Looking at what's in the patch queue, but not in the series file:
ext4-fix-hang-due-to-corrupted-jinode.patch
ext4-new-defm-options
ext4-online-resize-fix-for-group-descriptor-corruption.patch
Fix-EXT_MAX_BLOCK.patch
jbd2-dio-kjournal-race-EIO.patch
jbd-dio-kjournal-race-EIO.patch
ext2-printk-throttling
ext3_dx_readdir_hash_collision_fix.patch
ext3-printk-throttling
ext3_truncate_block_allocated_on_a_failed_ext3_write_begin.patch
Some of these are probably intentional (I think Ted has the printk
throttling stuff queued up to send) but have any of these simply gotten
lost somehow? Or merged upstream (or obsoleted) but not removed?
At least this one seems to be already applied:
ext4-online-resize-fix-for-group-descriptor-corruption.patch
so should probably be removed from git.
Unless someone knows offhand about the others, I can dig in and see what
might be going on....
For example:
http://repo.or.cz/w/ext4-patch-queue.git?a=commitdiff;h=70e9eefe6c0178e87068f675486a61727a1a48fb
dropped the jbd2-dio-kjournal-race-EIO.patch patch but from the commit
message, it's not clear that it was intentional...?
Thanks,
-Eric
next reply other threads:[~2008-09-14 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-14 21:11 Eric Sandeen [this message]
2008-09-14 21:34 ` patches in queue but missing from series? Theodore Tso
2008-09-14 21:43 ` Eric Sandeen
2008-09-15 6:32 ` Andreas Dilger
2008-09-15 18:10 ` Mingming Cao
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=48CD7DEC.6080008@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@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