mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bob Copeland" <me@bobcopeland.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	ath9k-devel@venema.h4ckr.net, ath5k-devel@venema.h4ckr.net,
	bkuhn@softwarefreedom.org
Subject: Re: [ath5k-devel] License of changes to ath5k/ath9k
Date: Tue, 25 Nov 2008 16:29:55 -0500	[thread overview]
Message-ID: <b6c5339f0811251329h1130fd4aladcbfda52f0542eb@mail.gmail.com> (raw)
In-Reply-To: <20081125210421.GF5950@tesla>

On Tue, Nov 25, 2008 at 4:04 PM, Luis R. Rodriguez
<lrodriguez@atheros.com> wrote:
> We'll keep using the ath5k Changes-licensed-under tag until we get
> advice from SFLC if we have done enough to ensure this is no longer
> necessary. For ath9k, if we are not sure if you have read the
> "Developer's Certificate of Origin 1.1" we may ping you with an e-mail
> just to be sure.

I don't consider any of my changes significant enough to confer copyright,
so by my Signed-off-by, I agree that whatever license the file currently
has is alright by me.  Even if the changes were significant, the previous
holds.

However, if everyone + SFLC prefers that we strictly use
Changes-licensed-under even if we don't claim copyright, then I'll
happily add the tag generator script to a git commit hook :)

> Ps. Please do not open any can of worms here, this is just informational.

Sure.  I like the ath9k way, but really it doesn't matter that much.

-- 
Bob Copeland %% www.bobcopeland.com

  reply	other threads:[~2008-11-25 21:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 21:04 Luis R. Rodriguez
2008-11-25 21:29 ` Bob Copeland [this message]
2008-11-25 22:28   ` [ath5k-devel] " Luis R. Rodriguez
2008-11-27  1:53     ` Bob Copeland
2008-12-02  4:49       ` Luis R. Rodriguez
2008-11-26 14:59 ` Bradley M. Kuhn

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=b6c5339f0811251329h1130fd4aladcbfda52f0542eb@mail.gmail.com \
    --to=me@bobcopeland.com \
    --cc=ath5k-devel@venema.h4ckr.net \
    --cc=ath9k-devel@venema.h4ckr.net \
    --cc=bkuhn@softwarefreedom.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.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®