From: Russell Cattelan <cattelan@redhat.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Cluster-devel] Re: [GFS2] Change argument of gfs2_dinode_out [17/70]
Date: Sun, 03 Dec 2006 13:06:53 -0600 [thread overview]
Message-ID: <4573204D.4070608@redhat.com> (raw)
In-Reply-To: <20061202011043.GG3078@ftp.linux.org.uk>
Al Viro wrote:
>On Fri, Dec 01, 2006 at 05:29:46PM -0600, Russell Cattelan wrote:
>
>
>
>>gfs2 is supposed to be stabilized and use-able for the up coming rhel5
>>release, not pretty up for somebody to print out and hang on their wall.
>>
>>
>
>Your insight, sir, is truly stunning. That is to say, it reminds of
>a sudden and unpleasant contact with something dense and misplaced.
>May I direct your attention to the fact that rhel5 is quite unlikely
>to be based on 2.6.20?
>
>
Ok your right rhel5 has no bearing on what goes into 2.6.20.
And again I not taking issues with any of the cleanups you sent
in they were complete and addressed real potential problems.
Just trying to point out stablizing and bug fixing over partial
cleanups would be more helpful
for gfs2 in general, for whatever kernel it is running in.
next prev parent reply other threads:[~2006-12-03 19:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 12:15 [GFS2] Change argument of gfs2_dinode_out [17/70] Steven Whitehouse
2006-12-01 19:19 ` Russell Cattelan
2006-12-01 19:25 ` Al Viro
2006-12-01 20:52 ` [Cluster-devel] " Russell Cattelan
2006-12-01 21:08 ` Al Viro
2006-12-01 23:29 ` Russell Cattelan
2006-12-02 1:10 ` Al Viro
2006-12-03 19:06 ` Russell Cattelan [this message]
2006-12-03 19:54 ` Christoph Hellwig
2006-12-03 22:44 ` Alan
2006-12-02 11:40 ` Pavel Machek
2006-12-03 20:21 ` Rik van Riel
2006-12-04 10:05 ` Steven Whitehouse
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=4573204D.4070608@redhat.com \
--to=cattelan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.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