From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Dey, Souvik" <sodey@sonusnet.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Issue with patchwork
Date: Thu, 22 Sep 2016 10:03:41 +0200 [thread overview]
Message-ID: <2561352.RYs4nfXb2h@xps13> (raw)
In-Reply-To: <BN3PR03MB14948F5311873E69FCFE3AF5DAC90@BN3PR03MB1494.namprd03.prod.outlook.com>
2016-09-22 00:20, Dey, Souvik:
> Hi All,
> I am sending git send-mail and the patch mail is also getting sent but I am not able see the patch in the patchwork link. Can someone point what might have gone wrong. It was working fine earlier though.
> Thanks in advance for any kind of help.
It happens sometimes because of a parsing error - maybe because you are
using Windows ;)
There is a fix in progress at patchwork. It will be applied as soon as
it is available.
In the meantime, a private email to me is sufficient. I'll do a manual
import.
prev parent reply other threads:[~2016-09-22 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 0:20 Dey, Souvik
2016-09-22 8:03 ` Thomas Monjalon [this message]
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=2561352.RYs4nfXb2h@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=sodey@sonusnet.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).