From: Linus Torvalds <torvalds@linux-foundation.org>
To: Mark Fasheh <mfasheh@suse.com>
Cc: linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
Joel Becker <joel.becker@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [git patches] Ocfs2 updates for 2.6.30
Date: Fri, 3 Apr 2009 12:13:11 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0904031208490.4015@localhost.localdomain> (raw)
In-Reply-To: <20090403184605.GC14571@wotan.suse.de>
On Fri, 3 Apr 2009, Mark Fasheh wrote:
>
> Here is the Ocfs2 changes for this merge window. I sent all these
> patches out to the list a couple weeks ago. Original mail is attached.
Hmm. And I can _guarantee_ that none of these patches were actually tested
as-is, because they were all rebased just minutes before the send.
- top commit:
Commit: Mark Fasheh <mfasheh@suse.com>
CommitDate: Fri Apr 3 11:39:26 2009 -0700
- email:
Date: Fri, 3 Apr 2009 11:46:05 -0700
From: Mark Fasheh <mfasheh@suse.com>
So any possible subtle interactions with any other changes would never
have been tested very much before the "please pull".
Are they likely? Probably not. But that's not the point. The point is that
you barely had time to compile that thing, much less give it any testing.
The whole "it compiles, it's perfect, ship it" mentality is _strictly_
only for me.
Quod licet Jovi, non licet bovi.
Linus
next prev parent reply other threads:[~2009-04-03 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 18:46 Mark Fasheh
2009-04-03 19:13 ` Linus Torvalds [this message]
2009-04-03 19:17 ` Linus Torvalds
2009-04-03 20:34 ` Mark Fasheh
-- strict thread matches above, loose matches on Subject: below --
2009-03-17 20:00 Mark Fasheh
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=alpine.LFD.2.00.0904031208490.4015@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=joel.becker@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
/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®