From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Paul Menage <paul-inf54ven1CmVyaH7bEyXVA@public.gmane.org>,
lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: linux-next: inclusion request for cgroup/for-next
Date: Tue, 22 Nov 2011 08:17:46 -0800 [thread overview]
Message-ID: <20111122161746.GB3250@google.com> (raw)
Hello, Stephen.
Can you please include the following branch into linux-next?
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-next
This is the new cgroup devel branch and will follow the usual
for-next/fixes branch convention.
Thanks a lot.
--
tejun
WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: lkml <linux-kernel@vger.kernel.org>,
Paul Menage <paul@paulmenage.org>, Li Zefan <lizf@cn.fujitsu.com>,
containers@lists.linux-foundation.org
Subject: linux-next: inclusion request for cgroup/for-next
Date: Tue, 22 Nov 2011 08:17:46 -0800 [thread overview]
Message-ID: <20111122161746.GB3250@google.com> (raw)
Hello, Stephen.
Can you please include the following branch into linux-next?
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-next
This is the new cgroup devel branch and will follow the usual
for-next/fixes branch convention.
Thanks a lot.
--
tejun
next reply other threads:[~2011-11-22 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 16:17 Tejun Heo [this message]
2011-11-22 16:17 ` linux-next: inclusion request for cgroup/for-next Tejun Heo
[not found] ` <20111122161746.GB3250-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2011-11-22 22:43 ` Stephen Rothwell
2011-11-22 22:43 ` Stephen Rothwell
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=20111122161746.GB3250@google.com \
--to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=paul-inf54ven1CmVyaH7bEyXVA@public.gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.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.