Re: [BK] upgrade will be needed
From: David Lang
Date: Mon Feb 14 2005 - 20:27:00 EST
On Mon, 14 Feb 2005 lm@xxxxxxxxxxxx wrote:
this does mean that there would be somehat of a commiter/non-commiter
split, with the difference between them being those who agree to the
non-compete license of #1 and those who don't and use #2 to have a local
read-only copy and have to use normal patches to submit changes up the
tree.
And how does the CVS gateway not provide this today? We effectively
have exactly what you are describing. And long ago I offered what I
called the tarball + patch server with an open source client for all
trees on bkbits.net - here it is: http://lkml.org/lkml/2003/12/14/47
If people had stopped flaming long enough to look at that it would
be installed on bkbits today and any repo hosted there would have an
automatic real-time gateway with no license problems. Heck, we could
even export the changeset comments into ChangeLog as Keith suggested
here: http://lkml.org/lkml/2003/12/14/92 .
the advantage over CVS would be the reduced network useage (both server
side and client side), but that's not worth the development costs you are
quoting.
since I don't have any problem with your license I had forgotten about
that other option. I was just trying to clarify what looked like a
misunderstanding of what was being asked and exploring options to reduce
the flaming.
People didn't seem interested and I came with the conclusion, rightly or
wrongly, that the vast majority of the people who did real work didn't
care about the license and the noisy people just wanted to pick a fight.
If I was wrong and this is valuable I can look into putting it up on
bkbits.net.
unfortunantly, you are probably right :-(
David Lang
--
There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.
-- C.A.R. Hoare
-
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/