From: Jeff Garzik <jeff@garzik.org>
To: Jacob Meuser <jakemsr@sdf.lonestar.org>
Cc: mcgrof@gmail.com, mickflemm@gmail.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath5k - License clarification
Date: Sat, 01 Sep 2007 15:38:42 -0400 [thread overview]
Message-ID: <46D9BFC2.4080707@garzik.org> (raw)
In-Reply-To: <20070901191405.GB10469@SDF.LONESTAR.ORG>
Was it slashdot or Theo's rant that made all the OpenBSD fanboys like
you come out of the woodwork?
Jeff
next prev parent reply other threads:[~2007-09-01 19:38 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 [this message]
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
-- 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=46D9BFC2.4080707@garzik.org \
--to=jeff@garzik.org \
--cc=jakemsr@sdf.lonestar.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=mickflemm@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;
as well as URLs for NNTP newsgroup(s).