mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: hch@infradead.org, swhiteho@redhat.com, torvalds@osdl.org,
	teigland@redhat.com, pcaulfie@redhat.com, kanderso@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: GFS2 and DLM
Date: Tue, 27 Jun 2006 01:50:05 -0700	[thread overview]
Message-ID: <20060627015005.21c20186.akpm@osdl.org> (raw)
In-Reply-To: <20060627083544.GA32761@elte.hu>

On Tue, 27 Jun 2006 10:35:44 +0200
Ingo Molnar <mingo@elte.hu> wrote:

> * Andrew Morton <akpm@osdl.org> wrote:
> 
> > On Tue, 27 Jun 2006 08:33:39 +0200
> > Ingo Molnar <mingo@elte.hu> wrote:
> > 
> > > Isnt this whole episode highly hypocritic to begin with?
> > 
> > Might be, but that's not relevant to GFS2's suitability.
> 
> it is relevant to a certain degree, because it creates a (IMO) false 
> impression of merging showstoppers. After months of being in -mm, and 
> after addressing all issues that were raised (and there was a fair 
> amount of review activity December last year iirc), one week prior the 
> close of the merge window a 'huge' list of issues are raised. (after 
> belovingly calling the GFS2 code a "huge mess", to create a positive and 
> productive tone for the review discussion i guess.)

It's a general problem - our reviewing resources do not have the capacity
to cover our coding resources.  This is especially the case on filesystems.
 We'd have merged (a very different) reiser4 a year ago if things were
in balance.

(and our code-breaking resources appear to exceed our code-fixing resources
too, but that's another topic).

  reply	other threads:[~2006-06-27  8:50 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20 12:17 Steven Whitehouse
2006-06-20 12:32 ` Nick Piggin
2006-06-20 12:47   ` Steven Whitehouse
2006-06-20 14:04     ` Nick Piggin
2006-06-20 15:40       ` Steven Whitehouse
2006-06-20 19:55         ` Andrew Morton
2006-06-21 11:20       ` Steven Whitehouse
2006-06-23 14:45       ` Christoph Hellwig
2006-06-26 21:03         ` Ingo Molnar
2006-06-27  7:52           ` Christoph Hellwig
2006-06-20 12:33 ` Christoph Hellwig
2006-06-20 12:55   ` Steven Whitehouse
2006-06-20 15:55   ` Ingo Molnar
2006-06-23 14:49 ` Christoph Hellwig
2006-06-23 20:46   ` Andrew Morton
2006-06-26 20:03   ` Ingo Molnar
2006-06-26 20:12     ` Arjan van de Ven
2006-06-27  7:08       ` Ingo Molnar
2006-06-27  6:33     ` Ingo Molnar
2006-06-27  6:43       ` Arjan van de Ven
2006-06-27  7:07         ` Ingo Molnar
2006-06-27  7:06       ` Andrew Morton
2006-06-27  8:35         ` Ingo Molnar
2006-06-27  8:50           ` Andrew Morton [this message]
2006-06-27  9:04             ` Ingo Molnar
2006-06-27  9:23               ` Andrew Morton
2006-07-03 13:40           ` Steven Whitehouse
2006-06-27  8:16       ` Nathan Scott
2006-06-27  8:22         ` Ingo Molnar
2006-06-27  8:41           ` Pekka Enberg
2006-06-27 10:33             ` Ingo Molnar
2006-06-27  8:42           ` Nathan Scott
2006-06-27  8:51             ` Ingo Molnar
2006-06-23 14:54 ` Christoph Hellwig
2006-06-23 15:54   ` Steven Whitehouse
2006-06-23 15:54     ` Christoph Hellwig
2006-06-23 16:09       ` Steven Whitehouse
2006-06-23 14:55 ` Christoph Hellwig
2006-06-23 14:57 ` Christoph Hellwig
2006-06-23 15:26   ` Steven Whitehouse
2006-06-23 15:00 ` Christoph Hellwig
2006-06-23 16:29   ` Steven Whitehouse
2006-06-23 16:48     ` Christoph Hellwig
2006-06-26 20:58       ` Ingo Molnar
2006-06-27  7:50         ` Christoph Hellwig
2006-06-27  8:31           ` Ingo Molnar

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=20060627015005.21c20186.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=kanderso@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pcaulfie@redhat.com \
    --cc=swhiteho@redhat.com \
    --cc=teigland@redhat.com \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®