From: "Wiles, Keith" <keith.wiles@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] scripts: relax line length check for fixed commit
Date: Sat, 25 Jun 2016 13:59:54 +0000 [thread overview]
Message-ID: <0C24FE9A-BF53-4FE1-A346-DA5CA6A5DA61@intel.com> (raw)
In-Reply-To: <20160624093043.GB13464@bricha3-MOBL3>
On 6/24/16, 4:30 AM, "dev on behalf of Bruce Richardson" <dev-bounces@dpdk.org on behalf of bruce.richardson@intel.com> wrote:
>On Fri, Jun 24, 2016 at 12:44:18AM +0200, Thomas Monjalon wrote:
>> It is better to keep the line "Fixes:" longer than 75 characters
>> than splitting.
>>
>> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
>
>Definite +1
Yes, +2 for me.
>
>Acked-by: Bruce Richardson <bruce.richardson@intel.com>
>
>
next prev parent reply other threads:[~2016-06-25 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 22:44 Thomas Monjalon
2016-06-24 9:30 ` Bruce Richardson
2016-06-25 13:59 ` Wiles, Keith [this message]
2016-06-27 14:54 ` Thomas Monjalon
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=0C24FE9A-BF53-4FE1-A346-DA5CA6A5DA61@intel.com \
--to=keith.wiles@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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 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).