> so in theory it's perfectly possible to 'link' the data's and metadata's
> license via BKL.txt - after all you already added licensing rules for the
> metadata into the BK license, for the purposes of OpenLogging.
It is our position and we believe that it is supported by the BKL license
that it is the right and authority of the original creator of the project
to enforce any license they so wish. If Linus wants to make it clear
that if you make changesets using BK that the checkin comments are also
GPLed, that's his right. That's our intent and that's what we believe
the license says. See clause 3(b).
> > By the way, the way this code works in bk-3.0 is that it saves a md5sum
> > or some sort of strong hash of the license in question and it will ask
> > you only once, assuming you are using the same home directory. It will
> > ask you again if the license changes, that's what the hash is for.
>
> this sounds really nice and unintrusive, how does one enable it? Is this
> BK_FORCE, or something else? I cannot find any reference to this in 'bk
> helptool'.
That's because we haven't shipped bk-3.0 yet, we expect to do so this
week. The license clause has been there for a long time, these rules are
part of the BKL. However, we only recently added the "click to accept"
stuff for the extra license and the lawyers tell us that is required to
be enforceable.
-- --- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 07 2002 - 22:00:57 EST