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

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

  • To: <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Thu, 16 Dec 2004 12:44:27 -0800
  • Delivery-date: Thu, 16 Dec 2004 20:45:25 +0000
  • List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
  • Thread-index: AcTjijjb8D7KxJwjRdiUyy92Atr91gAJVFFg
  • Thread-topic: [Xen-devel] Re: xen-unstable.bk

> We are now doing that. Try 'bk changes -t'. You'll see two
> 2.0.1-tagged changesets -- however, if you refer to that tag in any BK
> command then BK will always pick the right one (the later one).
> e.g., bk clone -rRELEASE-2.0.1 <src> <dst>

Great!  Thanks!  One more suggestion (if you aren't doing this
already):  Do something similar on the unstable tree;
whenever you have something that is relatively stable
(e.g. passes some basic tests), add a tag such as

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®.