From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Wright <chrisw@osdl.org>
Subject: Re: Bitkeeper
Date: Thu, 7 Apr 2005 23:55:25 -0700
Message-ID: <20050408065525.GD11199@shell0.pdx.osdl.net>
References: <1112911404.7186.75.camel@localhost.localdomain>
	<4255B1B7.2030403@diku.dk> <4255C1B7.6050509@tupshin.com>
	<20050407235521.GC29680@us.ibm.com> <4255CE7B.8050300@diku.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <4255CE7B.8050300@diku.dk>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jacob Gorm Hansen <jacobg@diku.dk>
Cc: Xen-devel@lists.xensource.com, Tupshin Harper <tupshin@tupshin.com>, Scott Parish <srparish@us.ibm.com>
List-Id: xen-devel@lists.xenproject.org

* Jacob Gorm Hansen (jacobg@diku.dk) wrote:
> With the recently announced open source bk client I suppose one could 
> create a script that would automatically track bk changes on a 
> per-changeset basis, including renames.

It might be tough.  That bk client doesn't really give you a bk repo.
It gives you a source tree and a file called ChangeLog, but no other
metadata.  So associating entries in ChangeLog with actual csets is best
guess.  You can pull a specific revision, so that plus a forest of cp
-rl trees and diff -Naur is conceptually feasible.  But I'm not sure how
well it would preserve bk merges.

thanks,
-chris