[Monotone-devel] Thoughts about 'testresult'...

[Richard Levitte - VMS Whacker]

Hi,

I've been thinking a little about the testresult situation from a few
days ago, and I've come to the conclusion that I really like the
concept, and most of the implementation.

The only real stumbling block is really the unexpected behavior.  If
you happen, just by chance, to update to a revision with a true
testresult ceert in it, you are suddenly "stuck", with no real
indication to why (monotone update will just not update).  That can be
quite a surprise!

I'm proposing to change that behavior by making things more explicit.
Instead of getting implicitely stuck on revisions with true testresult
certs, there should be a way to explicitely ask to get only those.  As
fat as I can tell, the simplest way would be with another selector.
Since we're talking about results, I propose 'r', with the following
format:

  r:keyid

keyid would simply be the key with which the testresult cert has been
signed, since that key is supposed to represent the test that has been
successfully performed.

Comments?  Is this a completely wacky idea, or would people like this
(I would, most obviously)?

Cheers,
Richard

-----
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.

-- 
Richard Levitte                         address@hidden
                                        http://richard.levitte.org/

"When I became a man I put away childish things, including
 the fear of childishness and the desire to be very grown up."
                                                -- C.S. Lewis