[Top][All Lists]

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

Re: [Gnu-arch-users] Sub-optimal ordering of rev-building in star-merge

From: Aaron Bentley
Subject: Re: [Gnu-arch-users] Sub-optimal ordering of rev-building in star-merge
Date: Thu, 11 Mar 2004 13:08:43 -0500
User-agent: Mozilla Thunderbird 0.5 (X11/20040217)

Stefan Monnier wrote:
- Aha the latest is 142, so let's built that.
- Aha the common ancestor is 135 so let's build that.

Since the second came after the first, 142 was build from 59 by applying
patches 60->142, while 135 was built from 59 as well by applying patch
Obviously, in this case the two steps should have been done in the
opposite order.  This was with tla-1.2

I hate that too, but it's impossible to know that 135 is the common ancestor before retrieving 142.

But it is being remedied: when my patches are merged, it will produce 135 by building backwards from 142.

If you have disk space to burn, you can use a non-sparse greedy revision library, so that when you need 135, it's available.


Aaron Bentley
Manager of Information Technology
Panometrics, Inc.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]