From: Neil Horman <nhorman@tuxdriver.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Accessing Virtual Function Device on Guest Machine using VFIO
Date: Fri, 5 Dec 2014 13:42:15 -0500 [thread overview]
Message-ID: <20141205184215.GE29245@hmsreliant.think-freely.org> (raw)
In-Reply-To: <5011667.KPTrBnDxk4@xps13>
On Fri, Dec 05, 2014 at 07:08:55PM +0100, Thomas Monjalon wrote:
> Hi,
>
> Please don't reply to a previous email to start a different topic.
> You can check how it looks here:
> http://thread.gmane.org/gmane.comp.networking.dpdk.devel
>
> > "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
>
> Please remove this disclaimer.
> It's not specifically against you but it's at least the tenth time I say this
> to an Aricent guy. This disclaimer should force us to remove your message
> (even in the archives). So we should maybe block all the emails from aricent.com.
>
+1. These disclaimers are not only most likely toothless (though IANAL), but it
does place the community in the position of either needing to take the effort to
scrub your emails from the archives to be in compliance with the disclamer, or
to take the legal risk that such a disclaimer actually has merit. If your
company can't abide by you removing such a notice, than that company can't
participate in open source.
Neil
> --
> Thomas
>
next prev parent reply other threads:[~2014-12-05 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 21:42 [dpdk-dev] [PATCH] librte_pmd_af_packet: add compile-time checks for kernel-specific options John W. Linville
2014-12-05 3:46 ` Neil Horman
2014-12-05 9:30 ` Thomas Monjalon
2014-12-05 16:24 ` John W. Linville
2014-12-05 16:37 ` Thomas Monjalon
2014-12-05 17:29 ` [dpdk-dev] Accessing Virtual Function Device on Guest Machine using VFIO Aashima Arora
2014-12-05 18:08 ` Thomas Monjalon
2014-12-05 18:42 ` Neil Horman [this message]
2014-12-05 21:14 ` [dpdk-dev] [PATCH] librte_pmd_af_packet: add compile-time checks for kernel-specific options Thomas Monjalon
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=20141205184215.GE29245@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).