All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.31 -mm merge plans
Date: Wed, 10 Jun 2009 20:08:41 +0100	[thread overview]
Message-ID: <20090610190841.GT8633@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20090610115140.09c9f4cb.akpm@linux-foundation.org>

On Wed, Jun 10, 2009 at 11:51:40AM -0700, Andrew Morton wrote:

> proc-merge-arrayc-into-basec.patch
> proc-merge-arrayc-into-basec-checkpatch-fixes.patch

I'm not sure that there's any point in that.  Sure, we can slap two
files together; what the hell for?  Both are quite large, there's
a (relatively) sane separation of code between them (misc. files
contents in /proc/<pid>/ vs. directory structure and symlinks in
there, more or less) and I don't see any benefit in mashing them
together.  Up to Alexey, but IMO that's pointless.

  parent reply	other threads:[~2009-06-10 19:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 18:51 2.6.31 -mm merge plans Andrew Morton
2009-06-10 19:00 ` mac80211-use-kzfree-in-key-handling-to-enforce-data-sanitization (was Re: 2.6.31 -mm merge plans) John W. Linville
2009-06-10 19:08 ` Al Viro [this message]
2009-06-10 19:16   ` 2.6.31 -mm merge plans Andrew Morton
2009-06-11  1:15     ` Amerigo Wang
2009-06-11  3:10       ` Al Viro
2009-06-11  5:25         ` Amerigo Wang
2009-06-13 20:53           ` Eric W. Biederman
2009-06-11  2:23 ` KOSAKI Motohiro
2009-06-11  2:23   ` KOSAKI Motohiro
2009-06-11 11:40 ` mmc_spi-use-eilseq-for-possible-transmission-errors.patch (was Re: 2.6.31 -mm merge plans) Matt Fleming

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=20090610190841.GT8633@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.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 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.