lkml.org 
[lkml]   [2004]   [Oct]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: BK kernel workflow
On Fri, Oct 29, 2004 at 07:19:05PM +0200, Ram?n Rey Vicente wrote:
> In Spain, reverse engineering is allowed for interoperability.

And in lots of other places. Which has been mentioned in this and other
instances of this discussion for the last 5 years. And the response is
that BK already gives you documented ways to interoperate, extensively
documented, in fact. You can get data and/or metadata into and out of
BK from the command line. You could create your own network protocol,
client, and server using the documented interfaces that BK has. You
could create your own CVS2BK tool, your own BK2CVS tool, etc., all
using documented interfaces.

The point of the interoperability hole is for commercial products
which try and lock up your data. We don't do that, in fact, we are
*dramatically* more open about getting data in and out, with all
the metadata, than any other commercial product. Go try and get the
same information from Perforce, Clearcase, or even CVS or Subversion.
Good luck.

Given that BK isn't hiding anything, the "reverse engineering for
interoperability" does not apply. Hello? Anyone listening? Didn't
think so. Sigh.
--
---
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/

\
 
 \ /
  Last update: 2005-03-22 14:07    [W:0.221 / U:0.320 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site