From: Johannes Berg <johannes@sipsolutions.net>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev01@lists.netfilter.org, Brenda Butler <bjb@mojatatu.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Richard Guy Briggs <rgb@tricolour.net>
Subject: Re: [netdev01] registration inconsistency
Date: Fri, 12 Dec 2014 14:19:51 +0100 [thread overview]
Message-ID: <1418390391.2470.45.camel@sipsolutions.net> (raw)
In-Reply-To: <548AE9AF.90902@mojatatu.com> (sfid-20141212_141219_330667_DC5C359F)
On Fri, 2014-12-12 at 08:12 -0500, Jamal Hadi Salim wrote:
> > Looking back at this, I think you meant that the *talks* were going to
> > be 50/50 like that, but some people have contacted me about that they
> > thought *attendance* was going to be like that. In fact I just glossed
> > over it and until now thought the same!
> >
> > If I'm right that you meant *talks* then I think you should clarify that
> > language and even send out a clarification as a reply to the CFP email.
> >
>
> I think i got it.
> Either a reply or we fix the CFP on the website.
> Ccing Richard.
I think a reply message would be good so it lands with those people who
might have gotten the original and misinterpreted it as well. Your
call :)
johannes
next prev parent reply other threads:[~2014-12-12 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1418326801.15709.1.camel@sipsolutions.net>
[not found] ` <5489F9B2.60306@mojatatu.com>
[not found] ` <1418375818.2470.0.camel@sipsolutions.net>
[not found] ` <548AD48A.9080009@mojatatu.com>
[not found] ` <1418387022.2470.26.camel@sipsolutions.net>
2014-12-12 13:12 ` [netdev01] registration inconsistency Jamal Hadi Salim
2014-12-12 13:19 ` Johannes Berg [this message]
2014-12-12 14:01 ` Richard Guy Briggs
2014-12-12 14:45 ` Jamal Hadi Salim
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=1418390391.2470.45.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=bjb@mojatatu.com \
--cc=jhs@mojatatu.com \
--cc=netdev01@lists.netfilter.org \
--cc=netdev@vger.kernel.org \
--cc=rgb@tricolour.net \
/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).