DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: Pankaj Gupta <pagupta@vmware.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Jochen Behrens <jbehrens@vmware.com>,
	Yong Wang <yongwang@vmware.com>,
	Sreeram Ravinoothala <sravinoothala@vmware.com>,
	"admin@dpdk.org" <admin@dpdk.org>
Subject: Re: Help:   e-mail did not go through to the dev@dpdk.org list.
Date: Mon, 2 May 2022 19:25:40 +0000	[thread overview]
Message-ID: <DM4PR12MB516736AB848480B0C9BF1F5FDAC19@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <BYAPR05MB56243764CF691359752A93C1C9FC9@BYAPR05MB5624.namprd05.prod.outlook.com>

> From: Pankaj Gupta <pagupta@vmware.com>
> Sent: Saturday, April 30, 2022 12:23 AM
> To: dev-request@dpdk.org <dev-request@dpdk.org>; dev@dpdk.org <dev@dpdk.org>
> Cc: Jochen Behrens <jbehrens@vmware.com>; Yong Wang <yongwang@vmware.com>; Sreeram Ravinoothala <sravinoothala@vmware.com>
> Subject: Help: e-mail did not go through to the dev@dpdk.org list. 
>
> Hi All,
> I sent 8 patches, twice today, but these patches are not visible in archive https://mails.dpdk.org/archives/dev/2022-April/thread.html.
> 
> 
> How do I figure out what went wrong with those emails?
 
Hello Pankaj,

Did you make sure the SMTP status was successful in git-send-email's output? Can you please double check for any errors and if there aren't any, provide the timestamp and message-id of one of the patches?

Thanks,
Ali

  reply	other threads:[~2022-05-02 19:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 21:23 Pankaj Gupta
2022-05-02 19:25 ` Ali Alnubani [this message]
2022-05-02 19:52   ` Pankaj Gupta

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=DM4PR12MB516736AB848480B0C9BF1F5FDAC19@DM4PR12MB5167.namprd12.prod.outlook.com \
    --to=alialnu@nvidia.com \
    --cc=admin@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=jbehrens@vmware.com \
    --cc=pagupta@vmware.com \
    --cc=sravinoothala@vmware.com \
    --cc=yongwang@vmware.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).