From: Jiri Slaby <jirislaby@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
James Morris <jmorris@namei.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: writable limits to -next [was: Adding to linux-next?]
Date: Mon, 26 Oct 2009 00:37:17 +0100 [thread overview]
Message-ID: <4AE4E12D.5070304@gmail.com> (raw)
In-Reply-To: <20091026095543.1bb1a25f.sfr@canb.auug.org.au>
On 10/25/2009 11:55 PM, Stephen Rothwell wrote:
> On Mon, 26 Oct 2009 09:47:41 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> On Fri, 23 Oct 2009 10:36:26 +0200 Jiri Slaby <jirislaby@gmail.com> wrote:
>>>
>>> Hi, could you please add git://decibel.fi.muni.cz/~xslaby/linux#limits
>>> into the -next tree?
>>
>> I have added it from today.
>
> It is actually git://decibel.fi.muni.cz/~xslaby/linux#writable_limits, right?
Hi. Oops, of course it is.
/me wondering: am I that dumb?
next prev parent reply other threads:[~2009-10-25 23:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 17:08 Adding to linux-next? Gregory Haskins
2009-10-06 11:57 ` Stephen Rothwell
2009-10-23 8:36 ` writable limits to -next [was: Adding to linux-next?] Jiri Slaby
2009-10-25 22:47 ` Stephen Rothwell
2009-10-25 22:55 ` Stephen Rothwell
2009-10-25 23:37 ` Jiri Slaby [this message]
2009-10-26 0:35 ` writable limits to -next Krzysztof Halasa
2009-10-26 0:35 ` Krzysztof Halasa
2009-10-26 1:04 ` Stephen Rothwell
2009-10-26 1:04 ` Stephen Rothwell
2009-10-26 13:04 ` Krzysztof Halasa
2009-10-26 13:04 ` Krzysztof Halasa
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=4AE4E12D.5070304@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--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 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.