Re: BK kernel workflow

[Larry McVoy]

> Actually it's not that simple.  With the free BK license it's not _your_ 
> choice that affects validity; It's the choice of any person at your 
> company deciding for everyone else.  So if one OSDL employee uses the 
> free BK licence, *nobody else* at OSDL can work on an SCM, even at home 
> in their spare time.  Technically, if any one of the other 10,000 people 
> at my university work on an SCM, I can't use it either since they pay 
> me.  I try to bury my head in the sand and think that they aren't.  In 
> reality however, I can't vouch for what the other 9,999 people are 
> doing.  

The reason it is worded that way is so that we avoid the situation where
one guy is doing the work on $SCM and the other guy is sitting there 
running BK commands in order to reverse engineer BK.

We aren't going to come make a fuss if you are using BK and some other
guy is tinkering with CVS, we're not unreasonable people.  On the other
hand, that doesn't give you carte blanche, if your officemate or friend
is working on a BK replacement and you are helping him, yes, we will 
likely make a fuss.
-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/