RE: BK question Re: [Xen-devel] BUG at domain.c:144

To:	"Adam Heath" <doogie@xxxxxxxxxxxxx>
Subject:	RE: BK question Re: [Xen-devel] BUG at domain.c:144
From:	"Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date:	Fri, 8 Apr 2005 11:27:07 +0100
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Fri, 08 Apr 2005 10:27:08 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcU7rVum0+l/CxkbTC++M6HSAA936QAd1OQg
Thread-topic:	BK question Re: [Xen-devel] BUG at domain.c:144

 
> > Can someone throw me some bk commands to speed up my 
> process a little?  
> > I'm looking to either automatically restore my bk tree to a 
> previous 
> > changeset (and removing all changesets thereafter), or a 
> way for bk to 
> > remove a changeset at a time, and I'll just script it.
> 
> How does the recent bk/linux issue affect xen?

It's a total pain in the ar*se. I expect we'll end up following whatever
Linux ends up doing, as the path of least resistance. 

It's a shame, as BK has worked really well for us.

Ian 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

WARNING - OLD ARCHIVES

xen-devel

RE: BK question Re: [Xen-devel] BUG at domain.c:144