From: vsnsdualce@memeware.net
To: leo_tck@volny.cz
Cc: Christopher Turkel <turkel.christopher@gmail.com>,
misc@openbsd.org, owner-misc@openbsd.org,
linux-kernel@vger.kernel.org, gentoo-user@lists.gentoo.org
Subject: Re: FU: RE: Why is no one discussing this anymore?
Date: Fri, 28 Dec 2018 17:22:04 +0000 [thread overview]
Message-ID: <4fca34d1b2c8a7f67c780b5df31f6d58@memeware.net> (raw)
In-Reply-To: <20181227235419.27A8ACE1@volny.cz>
I was addressing OpenBSD as-well, I chose the lists to CC to: linux
lists and BSD, since the underlying concerns are the same.
It took slightly longer to find the appropriate openbsd list, infact, so
you definitely weren't CC'd by accident.
On 2018-12-27 22:54, leo_tck@volny.cz wrote:
> zeur here.
>
> I now[0] see that a whole bunch of lists were Cc'd, and while I'm not
> sorry for not preserving the Ccs, I realize that you might not have
> been
> addressing us, misc@OpenBSD.org.
>
> I still think my point holds, though. This should be a matter of great
> concern for OpenBSD, like it is to just about every other project
> relying on licensed code, "open" or not.
>
> --zeur.
>
> [0] post-coffee-intake =)
>
>> This whole discussion is best served elsewhere.
prev parent reply other threads:[~2018-12-28 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 20:30 vsnsdualce
2018-12-27 20:48 ` Bon Onlines
2018-12-28 13:57 ` Theodore Y. Ts'o
2018-12-28 17:31 ` Why is no one discussing this anymore? - Attack the messaging rely, not the message! vsnsdualce
[not found] ` <CAKtRYpcHnGW9ftu7UaimH6RejgezeqNZW+rFkEm_GdYdGuXO5A@mail.gmail.com>
2018-12-27 20:57 ` Why is no one discussing this anymore? vsnsdualce
2018-12-27 21:53 ` Bernd Petrovitsch
2018-12-28 16:55 ` vsnsdualce
[not found] ` <20181227235419.27A8ACE1@volny.cz>
2018-12-28 17:22 ` vsnsdualce [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=4fca34d1b2c8a7f67c780b5df31f6d58@memeware.net \
--to=vsnsdualce@memeware.net \
--cc=gentoo-user@lists.gentoo.org \
--cc=leo_tck@volny.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=misc@openbsd.org \
--cc=owner-misc@openbsd.org \
--cc=turkel.christopher@gmail.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
all inboxes | Powered by JetHome®