From: Tejun Heo <tj@kernel.org>
To: Mandeep Singh Baines <msb@chromium.org>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
containers@lists.linux-foundation.org, cgroups@vger.kernel.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Oleg Nesterov <oleg@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Paul Menage <paul@paulmenage.org>
Subject: Re: [PATCH 1/5 V3] cgroup: remove redundate get/put of old css_set from migrate
Date: Tue, 20 Dec 2011 15:42:59 -0800 [thread overview]
Message-ID: <20111220234259.GO10752@google.com> (raw)
In-Reply-To: <20111220234131.GV13529@google.com>
Hello,
On Tue, Dec 20, 2011 at 03:41:31PM -0800, Mandeep Singh Baines wrote:
> > Either put this as part of patch description or if you don't want it
> > to be part of commit message, put it between --- and diffstat.
> > Unfortunately, no tool understands "-- >8 --".
> >
>
> git-am should. From "man git-am":
>
> -c, --scissors
> Remove everything in body before a scissors line (see git-
> mailinfo(1)).
>
> From "man git-mailinfo":
>
> --scissors
> Remove everything in body before a scissors line. A line that
> mainly consists of scissors (either ">8" or "8<") and perforation
> (dash "-") marks is called a scissors line, and is used to request
> the reader to cut the message at that line. If such a line appears
> in the body of the message before the patch, everything before it
> (including the scissors line itself) is ignored when this option is
> used.
>
> This is useful if you want to begin your message in a discussion
> thread with comments and suggestions on the message you are
> responding to, and to conclude it with a patch submission,
> separating the discussion and the beginning of the proposed commit
> log message with a scissors line.
>
> This can enabled by default with the configuration option
> mailinfo.scissors.
>
> But I can stop using scissors if that is what you prefer.
Heh, that's cute. If git-am is happy, I'm happy too. Thanks for
letting me know.
Thanks.
--
tejun
next prev parent reply other threads:[~2011-12-20 23:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 23:14 [PATCH 0/5] cgroup: some cleanups of cgroup_attach_proc Mandeep Singh Baines
2011-12-20 23:14 ` [PATCH 1/5 V3] cgroup: remove redundate get/put of old css_set from migrate Mandeep Singh Baines
2011-12-20 23:18 ` Tejun Heo
2011-12-20 23:41 ` Mandeep Singh Baines
2011-12-20 23:42 ` Tejun Heo [this message]
2011-12-20 23:46 ` Tejun Heo
2011-12-21 1:10 ` Li Zefan
2011-12-20 23:14 ` [PATCH 2/5] cgroup: remove redundant get/put of task struct Mandeep Singh Baines
2011-12-20 23:23 ` Tejun Heo
2011-12-21 0:04 ` Mandeep Singh Baines
2011-12-20 23:14 ` [PATCH 3/5] cgroup: only need to check oldcgrp==newgrp once Mandeep Singh Baines
2011-12-21 1:29 ` Li Zefan
2011-12-20 23:14 ` [PATCH 4/5] cgroup: remove extra calls to find_existing_css_set Mandeep Singh Baines
2011-12-20 23:30 ` Tejun Heo
2011-12-20 23:47 ` Mandeep Singh Baines
2011-12-20 23:14 ` [PATCH 5/5] cgroup: separate out cgroup_attach_proc error handling code Mandeep Singh Baines
2011-12-20 23:35 ` Tejun Heo
2011-12-21 0:02 ` Mandeep Singh Baines
2011-12-21 0:13 ` Tejun Heo
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=20111220234259.GO10752@google.com \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=msb@chromium.org \
--cc=oleg@redhat.com \
--cc=paul@paulmenage.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 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).