From: Valdis.Kletnieks@vt.edu
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Jan Kara <jack@ucw.cz>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] Re: 2.6.26-mmotm-0724 - linux-next.git loses /proc/sys/fs/quota, breaks disk quotas
Date: Sun, 27 Jul 2008 01:53:31 -0400 [thread overview]
Message-ID: <29790.1217138011@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sun, 27 Jul 2008 06:17:02 BST." <20080727051702.GY28946@ZenIV.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
On Sun, 27 Jul 2008 06:17:02 BST, Al Viro said:
> Wait... I remember fixing exactly that, but the fix is not in there...
> Bugger. Botched "fold on reorder", fortunately still findable in old local
> branch.
I guess we're fortunate that you remembered and found the fix - else this
would quickly have degenerated into a "How did it *ever* work?"..
> Sigh... Why does that stuff show up after 10 days in linux-next, about
> 5 minutes after seeing it merged into mainline? Murphy's fun...
I have to conclude that I'm the first person who actually tried the quota
support against either a linux-next or -mmotm kernel in the last 2 weeks,
which says something about our testing coverage.
Looking at the patch, I have to wonder what *else* was broken and nobody
noticed...
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
prev parent reply other threads:[~2008-07-27 5:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 2:22 Valdis.Kletnieks
2008-07-27 3:25 ` Andrew Morton
2008-07-27 3:43 ` Valdis.Kletnieks
2008-07-27 3:50 ` Roland Dreier
2008-07-27 4:09 ` Al Viro
2008-07-27 5:17 ` [PATCH] " Al Viro
2008-07-27 5:31 ` [PATCH] lost sysctl fix Al Viro
2008-07-27 6:29 ` Ingo Molnar
2008-07-27 6:35 ` Ingo Molnar
2008-07-27 6:31 ` Valdis.Kletnieks
2008-07-27 5:53 ` Valdis.Kletnieks [this message]
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=29790.1217138011@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=jack@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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
all inboxes | Powered by JetHome®