From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Parish Subject: Re: Bitkeeper Date: Thu, 7 Apr 2005 23:55:22 +0000 Message-ID: <20050407235521.GC29680@us.ibm.com> References: <1112911404.7186.75.camel@localhost.localdomain> <4255B1B7.2030403@diku.dk> <4255C1B7.6050509@tupshin.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4255C1B7.6050509@tupshin.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Tupshin Harper Cc: Xen-devel@lists.xensource.com, Jacob Gorm Hansen List-Id: xen-devel@lists.xenproject.org On Thu, Apr 07, 2005 at 04:26:47PM -0700, Tupshin Harper wrote: > Jacob Gorm Hansen wrote: > > Cool. I'm interested in tracking it with darcs, myself. I'm curious what > process/scripts you're using to do the tracking. cd ~/darcs/BK-xen-unstable ~/bin/bk_client-1.1/update bk://xen.bkbits.net/xeno-unstable.bk darcs add -r * darcs record -am "merge with bk://xen.bkbits.net/xeno-unstable.bk" I keep BK-xen-unstable as a clean mirror, updated daily. For dev work i branch off that, and stay in sync using "darcs pull". Unfortunately, this isn't granular to individual bk patches, and renames show up as del/adds. sRp -- Scott Parish