From: Jeff Garzik <jeff@garzik.org>
To: Bob Beck <beck@bofh.cns.ualberta.ca>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev <netdev@vger.kernel.org>
Subject: Re: r.kernel.org
Date: Sat, 01 Sep 2007 21:13:31 -0400 [thread overview]
Message-ID: <46DA0E3B.1080509@garzik.org> (raw)
In-Reply-To: <20070902001913.GF24887@bofh.cns.ualberta.ca>
Bob Beck wrote:
>
>> I urge developers to not bait into this and just leave this alone.
>> Those involved know what they are doing and have a strong team of
>> attorneys watching their backs. Any *necessary* discussions are be
>> done privately.
>>
>> Luis
>
> What? when we talk about the ethics of cooperating development
> and sharing code the response is "we have lawyers watching your backs"
> and "we know what we are doing and have a plan"
>
> What is this? a concerted attack by some organization on
> the BSD projects? Would that be the FSF? or freesoftware.org?
>
> What kind of crap is this? that Free Software developers can't
> respect each others project goals and work together, but instead should
> beware of organizations with hidden agendas to abscond with their work.
>
> What a crock. I urge any developers involved to decide if
> you really want to work in an environment of this sort of amoral baloney.
Your BSD software appears to have a bug in it. Your email's CC line was
truncated at "netdev@vge", with the rest spilling into your email's
subject line.
I'll wager this bug also triggered a buffer overflow on your side,
leading to an unwanted public spew of anti-Linux conspiracy theories.
But don't worry, we find them entertaining nonetheless.
Jeff
prev parent reply other threads:[~2007-09-02 1:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 0:19 r.kernel.org Bob Beck
2007-09-02 1:13 ` Jeff Garzik [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=46DA0E3B.1080509@garzik.org \
--to=jeff@garzik.org \
--cc=beck@bofh.cns.ualberta.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.