From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: John McNamara <john.mcnamara@intel.com>, dpdk-web <web@dpdk.org>
Subject: Re: [dpdk-web] Reviewathon
Date: Sat, 23 Jun 2018 14:15:08 +0200 [thread overview]
Message-ID: <1582816.gTkhrkM3Gq@xps> (raw)
In-Reply-To: <f275a276-4a35-6ddf-f2a3-6298e5cc868c@intel.com>
22/06/2018 17:43, Ferruh Yigit:
> > IRC freenode #dpdk-board
> > web client: https://webchat.freenode.net/
>
> Hi Thomas,
>
> I can't find the IRC channel information in web page, there is a reference
> related to thechboard meeting [3] but not mentioned anywhere as a generic
> communication channel.
>
> What do you think adding some documentation related to DPDK IRC channel?
Yes, absolutely, it is a miss.
When advertising IRC, we need to explain that it is for quick synchro
but the important informations must be sent to the mailing list
in order to be archived and seen by everybody interested.
parent reply other threads:[~2018-06-23 12:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <f275a276-4a35-6ddf-f2a3-6298e5cc868c@intel.com>]
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=1582816.gTkhrkM3Gq@xps \
--to=thomas@monjalon.net \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=web@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).