All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: dhowells@redhat.com, tytso@mit.edu
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: - disable-ext4.patch removed from -mm tree
Date: Sun, 3 Feb 2008 12:25:51 -0800	[thread overview]
Message-ID: <20080203122551.6830370a.akpm@linux-foundation.org> (raw)
In-Reply-To: <200802032018.m13KIGoC029855@imap1.linux-foundation.org>

On Sun, 03 Feb 2008 12:18:35 -0800 akpm@linux-foundation.org wrote:

> 
> The patch titled
>      disable-ext4
> has been removed from the -mm tree.  Its filename was
>      disable-ext4.patch

I dropped the entire ext4 patch series, because the newly-added
convert-to-iget_locked patch has wrecked the iget-coversion patch which I
have queued.  Please do not merge that patch under my feet.

When I merge David's iget coversion patches this will instead wreck the
ext4 patchset.

Dunno what to do about this sort of thing, apart from encouraging
developers to take a look at what's happening in other trees before merging
stuff.

  reply	other threads:[~2008-02-03 20:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 20:18 - disable-ext4.patch removed from -mm tree akpm
2008-02-03 20:25 ` Andrew Morton [this message]
2008-02-04  1:36   ` Theodore Tso
2008-02-04  3:15     ` Andrew Morton
2008-02-04 15:00       ` Theodore Tso
2008-02-04 20:11         ` Andrew Morton
2008-02-04 20:30           ` Theodore Tso
2008-02-05  9:40           ` David Howells
2008-02-05 21:26         ` Mingming Cao
2008-02-06  1:02           ` Mingming Cao
2008-02-06  1:57             ` Andrew Morton
2008-02-06  2:21               ` Mingming Cao
2008-02-04 20:24       ` merge plans, was " Christoph Hellwig
2008-02-04 22:35         ` Andrew Morton
2008-02-05  9:44           ` Christoph Hellwig
2008-02-05  9:53             ` Andrew Morton

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=20080203122551.6830370a.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.