From: Pavel Machek <pavel@ucw.cz>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Writable limits (was Re: Linux 2.6.34-rc1)
Date: Tue, 23 Mar 2010 14:59:25 +0100 [thread overview]
Message-ID: <20100323135925.GA1703@ucw.cz> (raw)
In-Reply-To: <alpine.LRH.2.00.1003132252160.12517@twin.jikos.cz>
Hi!
> > > It's out there now. I still have a few trees I already got pull requests
> > > for, and that I want to look over a bit more (ceph, gdb tree etc), and
> > > it's possible that I've just overlooked some other pull request.
> > >
> > > So if you feel like you sent me a pull request bit might have been
> > > over-looked, please point that out to me
> >
> > Hi, yes, the writable limits tree:
> > http://lkml.org/lkml/2010/3/5/219
> >
> > Maybe it was ignored on purpose. Either way, I would like to know to
> > decide whether to drop it from -next or not and wait for a 2.6.35 merge
> > window.
>
> Seems like this was neither commented on, nor merged. I don't see any
> serious objections to having this merged having been raised anywhere ...
>
> Any word on this?
Maybe noone cars? Try to push it through akpm?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2010-03-23 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 20:33 Linux 2.6.34-rc1 Linus Torvalds
2010-03-08 22:06 ` Jiri Slaby
2010-03-13 21:56 ` Writable limits (was Re: Linux 2.6.34-rc1) Jiri Kosina
2010-03-23 13:59 ` Pavel Machek [this message]
2010-03-09 2:14 ` Linux 2.6.34-rc1 Mike Frysinger
2010-03-09 16:28 ` Jan Kara
2010-03-09 17:13 ` Randy Dunlap
2010-03-11 15:08 ` Please pull UDF updates for 2.6.34-rc1 Jan Kara
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=20100323135925.GA1703@ucw.cz \
--to=pavel@ucw.cz \
--cc=jirislaby@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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.