[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Re: xen-unstable.bk

  • To: "Adam Sulmicki" <adam@xxxxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Thu, 16 Dec 2004 08:03:18 -0800
  • Cc: <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 16 Dec 2004 16:07:36 +0000
  • List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
  • Thread-index: AcTjLnuYbBR4yB5NTNSp4W2NbtPx/wAWPQ4Q
  • Thread-topic: [Xen-devel] Re: xen-unstable.bk

Thanks for the reply.  IIRC, the bk revision number is not
guaranteed to remain constant across time, correct?  E.g.
if someone checks in a branch based on a previous version,
do the later branch numbers change?

In any case, I'm still wondering if it might be time to have
some kind of fixed release mechanism, perhaps starting with 2.0.2?.
Is it at least possible to tag a bk revision (as in CVS)
so "bk clone -rXEN_2_0_2 ..." works as expected and always
gets the same bits?  Otherwise, using the method Adam suggests to
select a version to base a patch off of is kind of a crapshoot.


> -----Original Message-----
> From: Adam Sulmicki [mailto:adam@xxxxxxxxxxxx] 
> Sent: Wednesday, December 15, 2004 10:36 PM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Re: xen-unstable.bk
> > Is there anyway (using bk magic or otherwise) to get a guaranteed
> > unchanging version of a Xen release?  Since all three trees
> > periodically get updated for bug fixes, its hard to create a
> > patch which applies cleanly to any Xen release because the bits
> > may change from one day to the next.
> well, not impossible but not entirely trival either, in
>       http://sourceforge.net/mailarchive/message.php?msg_id=10230752
> I had refered to beta version of xen 2.0
>       bk clone -r1.1397.1.5 bk://xen.bkbits.net/xen-2.0.bk
> I had some ppl donwloading the same revision of bk and 
> applying my patch 
> so I know it works.
> You can find the revision number from
>       http://xen.bkbits.net:8080/xen-2.0.bk/ChangeSet?nav=index.html
> (maybe there's some better way but I haven't found it yet... 
> you can look 
> up the ChangeSet on your disk to see the date of last 
> checkout.. look for 
> the 2nd string with "2004" at top of the file).

SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.