linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Greg KH <greg@kroah.com>
Cc: Chris Wedgwood <cw@f00f.org>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: linux-next: Tree for May 1 (devtmpfs)
Date: Sat, 2 May 2009 03:01:44 -0400	[thread overview]
Message-ID: <20090502070144.GA19849@infradead.org> (raw)
In-Reply-To: <20090501225616.GA18064@kroah.com>

On Fri, May 01, 2009 at 03:56:16PM -0700, Greg KH wrote:
> As we discussed on irc, I think you no longer object to this, and see
> how it solves a real problem, and can probably help out your initramfs
> tools.

I defintively objet to the implementation, I'm in the process of writing
up the objections.  I must say I'm generally disappointed how fast
controversial stuff ends up in linux-next.  At least your tree
traditionally was quilt series so it can be dropped, unlike some other
people sucking stuff into gigantic git trees that never get rebased :P

      reply	other threads:[~2009-05-02  7:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-01  6:34 linux-next: Tree for May 1 Stephen Rothwell
2009-05-01 15:18 ` linux-next: Tree for May 1 (tmpfs) Randy Dunlap
2009-05-02  5:24   ` Stephen Rothwell
2009-05-01 15:25 ` linux-next: Tree for May 1 (comedi) Randy Dunlap
2009-05-01 15:28 ` linux-next: Tree for May 1 (devtmpfs) Randy Dunlap
2009-05-01 16:51   ` Kay Sievers
2009-05-01 16:55   ` Chris Wedgwood
2009-05-01 22:56     ` Greg KH
2009-05-02  7:01       ` Christoph Hellwig [this message]

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=20090502070144.GA19849@infradead.org \
    --to=hch@infradead.org \
    --cc=cw@f00f.org \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).