Re: [BK] upgrade will be needed

From: Larry McVoy (lm_at_bitmover.com)
Date: 02/15/05

  • Next message: Nigel Cunningham: "Re: PATCH: Address lots of pending pm_message_t changes" 
    Date:	Mon, 14 Feb 2005 16:03:43 -0800
To: David Lang <david.lang@digitalinsight.com>

    On Mon, Feb 14, 2005 at 03:23:47PM -0800, David Lang wrote:
    > Larry, I don't think he's talking about making the free bk be a striped
    > down version, I think he's talking about having two different free
    > versions.

    Leaving aside the $600K/year or so it would cost us to do that...

    > 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 .

    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. 

    -- 
---
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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
  • Next message: Nigel Cunningham: "Re: PATCH: Address lots of pending pm_message_t changes"

    Relevant Pages

    • Re: kgdb for mainline kernel: core-lite [patch 1/3]
      ... This feature lets gdb hook onto a kernel function to detect loading and ... unloading of modules and preserves module section information for later use ... The one in my tree also apparently works to some ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • [RFC] removal of legacy cdrom drivers (Re: [PATCH] mcdx.c insanity removal)
      ... bar and baz and fairly long expressions. ... if we want to keep the FPOS in the tree. ... Driver is obviously ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • RE: arch/xen is a bad idea
      ... > The Xen team still believe that it's best to keep arch/xen, ... I'd hope that we could get xen into the main-line tree. ... This is going to require some significant i386 code refactoring, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.0-test9-mjb1
      ... > scheduler callers profiling ... any e1000 fixes you have, please forward them to me and Intel ... rather than letting them languish in a tree. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: post 2.6.7 BK change breaks Java?
      ... > wouldn't expect either Linus or Andrew to have decided to merge an NX ... Linus' tree. ... how do I tell BitKeeper "pull up to revision..."? ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)