From: Jacob Meuser <jakemsr@sdf.lonestar.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Jeff Garzik <jeff@garzik.org>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath5k - License clarification
Date: Sat, 1 Sep 2007 21:27:37 +0000 [thread overview]
Message-ID: <20070901212737.GD23642@SDF.LONESTAR.ORG> (raw)
In-Reply-To: <1188681271.7585.163.camel@johannes.berg>
On Sat, Sep 01, 2007 at 11:14:31PM +0200, Johannes Berg wrote:
> On Sat, 2007-09-01 at 21:04 +0000, Jacob Meuser wrote:
>
> > I already explained my reasons for interest.
> >
> > It has nothing to do with what license is which, but about respect
> > for the original author's wishes and the general idea of giving back.
> >
> > why are you attacking me?
>
> Wait, so you're suddenly the poor victim of an attack when you
> contribute nothing to linux wireless and then out of the blue show up on
> our mailing list and tell us how bad we are behaving? Cute.
sorry if you feel that I am trying to scold you. this isn't
about linux-wireless and these particular patches per se, but
AFAICS, as a general developer, a common issue of license
incompatability.
I am only using this forum because it seems "warm" on this
subject, and I've really said all I have to say.
--
jakemsr@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
next prev parent reply other threads:[~2007-09-01 21:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-01 19:14 [PATCH] ath5k - License clarification Jacob Meuser
2007-09-01 19:38 ` Jeff Garzik
2007-09-01 20:07 ` Jacob Meuser
2007-09-01 20:32 ` Jeff Garzik
2007-09-01 21:04 ` Jacob Meuser
2007-09-01 21:14 ` Johannes Berg
2007-09-01 21:27 ` Jacob Meuser [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-02 13:42 Mark Kettenis
2007-09-02 14:39 ` Johannes Berg
2007-08-31 16:18 Luis R. Rodriguez
2007-08-31 16:43 ` Luis R. Rodriguez
2007-08-31 16:53 ` Sam Leffler
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=20070901212737.GD23642@SDF.LONESTAR.ORG \
--to=jakemsr@sdf.lonestar.org \
--cc=jeff@garzik.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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 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).