From: Josh Triplett <josh@freedesktop.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [patchset] rewrite of initializer handling
Date: Mon, 18 Jun 2007 11:02:55 -0700 [thread overview]
Message-ID: <4676C8CF.6020201@freedesktop.org> (raw)
In-Reply-To: <alpine.LFD.0.98.0706181002590.14121@woody.linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
Linus Torvalds wrote:
> On Mon, 18 Jun 2007, Al Viro wrote:
>> Current tree handling of initializers is rather incomplete
>> and in many cases broken. Patchset rewrites that stuff pretty much
>> from scratch; AFAICS it works.
>
> Josh - you may already be aware of it, but I thought I'd point it out
> anyway: when Al Viro sends me a patch (or set of patches), I personally
> just realize that a superior intellect has contacted me, told me I'm
> wrong, and given me the keys to fix it.
>
> IOW, Al's patches tend to be a good point to just say "Oh, ok, I was a
> moron for ever writing anything else, thank you for not pointing it out
> any more impolitely and not chewing my head off", and then just applying
> or pulling them.
>
> Which is not to say that I've never gotten a patch without a bug in it
> from Al, but I've never seen Al do something that wasn't fundamentally the
> "Right Thing(tm)" to do.
>
> IOW, Al is one of those few people where I can just close my eyes and say
> "yup, I'll apply it" without even bothering to look at the patch.
Yeah, I've observed the same thing from activity in both the kernel community
and the Sparse community. I still look at the patches, but primarily so I
can understand them and learn something from them, not because I expect to
find anything wrong. :)
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-06-18 18:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 10:19 [patchset] rewrite of initializer handling Al Viro
2007-06-18 10:26 ` Al Viro
2007-06-18 17:07 ` Linus Torvalds
2007-06-18 18:02 ` Josh Triplett [this message]
2007-06-18 19:30 ` Al Viro
2007-06-18 18:19 ` Josh Triplett
2007-06-18 19:16 ` Al Viro
2007-06-18 19:27 ` Linus Torvalds
2007-06-18 21:46 ` Michael Stefaniuc
2007-06-18 22:43 ` Al Viro
2007-06-19 9:47 ` Michael Stefaniuc
2007-06-19 20:15 ` Michael Stefaniuc
2007-06-19 22:41 ` Al Viro
2007-06-20 8:54 ` Michael Stefaniuc
2007-06-20 21:29 ` Michael Stefaniuc
-- strict thread matches above, loose matches on Subject: below --
2007-06-19 17:12 Alexey Dobriyan
2007-06-19 17:21 ` Al Viro
2007-06-19 22:33 ` Al Viro
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=4676C8CF.6020201@freedesktop.org \
--to=josh@freedesktop.org \
--cc=linux-sparse@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).