All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan <alan@lxorguk.ukuu.org.uk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Russell Cattelan <cattelan@redhat.com>,
	Al Viro <viro@ftp.linux.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [Cluster-devel] Re: [GFS2] Change argument of gfs2_dinode_out [17/70]
Date: Sun, 3 Dec 2006 22:44:19 +0000	[thread overview]
Message-ID: <20061203224419.794a6bc6@localhost.localdomain> (raw)
In-Reply-To: <20061203195422.GA9762@infradead.org>

> The right thing would have been to no put in gfs2 too early.  According
> to you it's unstable.

I would note that Russell is expressing his own slightly odd view not a
company one, nor afaik the view of any of the mainstream GFS2 team.


  reply	other threads:[~2006-12-03 22:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30 12:15 [Cluster-devel] [GFS2] Change argument of gfs2_dinode_out [17/70] Steven Whitehouse
2006-11-30 12:15 ` Steven Whitehouse
2006-12-01 19:19 ` [Cluster-devel] " Russell Cattelan
2006-12-01 19:19   ` Russell Cattelan
2006-12-01 19:25   ` [Cluster-devel] " Al Viro
2006-12-01 19:25     ` Al Viro
2006-12-01 20:52     ` [Cluster-devel] " Russell Cattelan
2006-12-01 20:52       ` Russell Cattelan
2006-12-01 21:08       ` Al Viro
2006-12-01 21:08         ` Al Viro
2006-12-01 23:29         ` Russell Cattelan
2006-12-01 23:29           ` Russell Cattelan
2006-12-02  1:10           ` Al Viro
2006-12-02  1:10             ` Al Viro
2006-12-03 19:06             ` Russell Cattelan
2006-12-03 19:54               ` Christoph Hellwig
2006-12-03 22:44                 ` Alan [this message]
2006-12-02 11:40           ` Pavel Machek
2006-12-02 11:40             ` Pavel Machek
2006-12-03 20:21             ` Rik van Riel
2006-12-03 20:21               ` Rik van Riel
2006-12-04 10:05   ` Steven Whitehouse
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=20061203224419.794a6bc6@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=cattelan@redhat.com \
    --cc=hch@infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.