From: Ben Pfaff <blp@cs.stanford.edu>
To: David Miller <davem@davemloft.net>
Cc: pshelar@nicira.com, netdev@vger.kernel.org, jesse@nicira.com
Subject: Re: [PATCH v2] IP_GRE: Fix kernel panic in IP_GRE with GRE csum.
Date: Tue, 22 Jan 2013 21:08:33 -0800 [thread overview]
Message-ID: <877gn4iizy.fsf@blp.benpfaff.org> (raw)
In-Reply-To: <20130122.205507.339713494072219737.davem@davemloft.net> (David Miller's message of "Tue, 22 Jan 2013 20:55:07 -0500 (EST)")
David Miller <davem@davemloft.net> writes:
> From: Pravin B Shelar <pshelar@nicira.com>
> Date: Tue, 22 Jan 2013 14:56:38 -0800
>
>> Fixed code indentation according to comments from David Miller.
>>
>> --8<--------------------------cut here-------------------------->8--
>
> This doesn't do what you think it does. No automated tool is going
> to edit the commit message the way you think this will.
"git am" does if you run with --scissors, see git-am(1):
-c, --scissors
Remove everything in body before a scissors line (see git-
mailinfo(1)).
and git-mailinfo(1);
--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.
next prev parent reply other threads:[~2013-01-23 5:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 22:56 [PATCH v2] IP_GRE: Fix kernel panic in IP_GRE with GRE csum Pravin B Shelar
2013-01-23 1:55 ` David Miller
2013-01-23 5:08 ` Ben Pfaff [this message]
2013-01-23 5:20 ` David Miller
2013-01-23 14:00 ` YOSHIFUJI Hideaki
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=877gn4iizy.fsf@blp.benpfaff.org \
--to=blp@cs.stanford.edu \
--cc=davem@davemloft.net \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
/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.