If you just want to send him regular patches, use bk export -tpatch.
That's sort of a lame way to go if you are using BK on both ends,
you're going to end up merging your changes with your changes when
you pull from Linus' tree. There are lots of reasons why this isn't
a good idea.
> We were planning on setting up a clone for non-Namesys users outside our
> firewall, but we need for Linus's access to be just as secure as ours.
bk help url, then look at
Connects to <host> using ssh, assumes that bkd is the
login shell. The home directory of <user> must be the
root of the repository.
then you can make a login shell that looks like
exec bk bkd -xcd
and you have an ssh based login which can only look at data in that
directory. This is how the write path on bkbits.net works.
> Another model you might consider, one which would probably make you more
> money, make us happier, and better avoid "freeloaders", would be to make
> bitkeeper free for use with free software only. This would be rather
> similar to what I use for reiserfs, which is free for use with free
> operating systems only, and available for a fee for all others. It
> allows you to "do unto others as they would do unto you" (The Reiser
> Rule ;-) ).
We are dealing with various commercial organizations who play games
with the checkin comments so that they can use BK for free and not give
up any information. Technically, it's a violation of the license if
they do that, but proving that they are doing it just isn't worth it.
What I'm tempted to do is to figure out a reasonable way to force free
uses to make their changes publically available. More like sourceforge,
if you use their service, anyone can get at your source. The problem
is that we can't force all the changes out into the open immediately,
people may have good reasons to hide (security changes, for example),
along with bad reasons (they're freeloaders).
Allowing free use of BK with free software only doesn't solve anything.
We have lots of people doing that and still hiding their changes
behind empty (or "fixed") checkin comments. It's only the commercial
organizations who are a problem. I'd really like to force those changes
out in the open if they aren't going to pay. The whole point of the
openlogging stuff was to get people to work out in the open.
I've thought a bit about some sort of answer which addresses this and
I'm curious to see what people would think if the rule were that your
changes had to show up on a public server within a given time period
(a month? 2 months? 3 months?). In other words, factor in a reasonable
ability to work in privacy but make it be limited enough that it only
works for truly free software.
My definition of free software is anything where the source is publically
available. It's sometimes called "Open Source". Open source software
where you can't get at the source is lame.
----- 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 firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/