Newbie question

[Douglas Philips]

On or about 2009 Feb 1, at 1:06 PM, Derek Scherger indited:
> On Thu, Jan 29, 2009 at 8:47 AM, Douglas Philips wrote:
>> That is a policy decision. And if bisect enforces a policy decision  
>> it
>> is broken. period.
>
> I had this problem the other day, not with mercurial bisect mind  
> you, but I don't think it matters. If the you can't build any  
> particular revision you can't determine whether or not that revision  
> introduced a bug or if it contained a bug or not. So, with a  
> frequently failing build, bisect just doesn't work very well.

Whether or not every single changeset "can be built" is a policy  
decision.
It is a policy decision that might be expressed, for example, with the  
'group' extension if that particular formality fits your policy.
It is a policy decision how 'intermediate' changesets and 'merge'  
changesets are indicated.
(It may well be that your policy is that only merge changesets are  
testable with bisect.)

Fortunately bisect was recently modified so that it can skip  
changesets. That doesn't help your other tool of course...

--Doug