From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] scripts: add git hook scripts for checkpatch and auto doc generation
Date: Fri, 6 Nov 2015 14:03:39 +0000 [thread overview]
Message-ID: <20151106140339.GA9248@sivlogin002.ir.intel.com> (raw)
In-Reply-To: <1446817732-17873-1-git-send-email-ferruh.yigit@intel.com>
On Fri, Nov 06, 2015 at 01:48:51PM +0000, Ferruh Yigit wrote:
> Sorry for duplication, previous patch is not in the patchwork, this is the
> exact same patch and re-sent for patchwork.
>
Incase anybody interested patchwork error seems because of a special char in message header "Received" field.
Failed ones has: "... with œ id ..."
Not sure why specific host appends this char.
Thanks,
ferruh
next prev parent reply other threads:[~2015-11-06 14:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 23:22 Ferruh Yigit
2015-11-06 13:48 ` Ferruh Yigit
2015-11-06 13:48 ` Ferruh Yigit
2015-11-24 17:44 ` Thomas Monjalon
2015-11-24 18:04 ` Ferruh Yigit
2015-11-06 14:03 ` Ferruh Yigit [this message]
2015-11-27 14:34 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2015-12-03 19:09 ` Thomas Monjalon
2015-12-07 13:32 ` Ferruh Yigit
2015-12-07 15:06 ` [dpdk-dev] [PATCH v3] " Ferruh Yigit
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=20151106140339.GA9248@sivlogin002.ir.intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.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).