Re: [Monotone-devel] Re: Best practice using monotone

Touche. My case slipped... On 04/09/06, Bruce Stephens <[EMAIL PROTECTED]> wrote: "Andy Jones" <[EMAIL PROTECTED]> writes: > More good stuff. Don't think I've seen that H selector documented anywhere..., h is in the manual, . H doesn't

[Monotone-devel] Re: Best practice using monotone

"Andy Jones" <[EMAIL PROTECTED]> writes: > More good stuff. Don't think I've seen that H selector documented anywhere..., h is in the manual, . H doesn't yet exist, as far as I know. There's a possible meaning on the wiki

Re: [Monotone-devel] Re: Best practice using monotone

More good stuff. Don't think I've seen that H selector documented anywhere..., On 25/08/06, Nathaniel Smith <[EMAIL PROTECTED]> wrote: On Thu, Aug 24, 2006 at 06:36:10PM +0100, Andy Jones wrote: > I know it's a pain but really, ideally, this is a bug. Either the > system should cope with multi

Re: [Monotone-devel] Re: Best practice using monotone

On Thu, Aug 24, 2006 at 06:36:10PM +0100, Andy Jones wrote: > I know it's a pain but really, ideally, this is a bug. Either the > system should cope with multiple identical tags, or it shouldn't allow > you to make them.Principal of least astonishment. It does cope -- it says "there are multi

Re: [Monotone-devel] Re: Best practice using monotone

On Thu, Aug 24, 2006 at 12:30:06PM -0500, Chad Walstrom wrote: > "Andy Jones" <[EMAIL PROTECTED]> wrote: > > Alternatively I could just write a script that did 'mtn update -r t:test' ! > > > > (Um, that +would+ get the +latest+ revision with that tag, right?) > > No. Tags are a different beast

Re: [Monotone-devel] Re: Best practice using monotone

Exactly: multiple tags can't be prevented. And monotone does cope with them. It's just that they don't work in quite the way you might expect. ::grin:: you mean that it copes with them by raising an error? Must be some strange new definition of "cope" that I was previously unaware of... Thin

Re: [Monotone-devel] Re: Best practice using monotone

"Andy Jones" <[EMAIL PROTECTED]> writes: > I know it's a pain but really, ideally, this is a bug. Either the > system should cope with multiple identical tags, or it shouldn't allow > you to make them.Principal of least astonishment. > > I guess you would have to cope with them, since you can

Re: [Monotone-devel] Re: Best practice using monotone

I know it's a pain but really, ideally, this is a bug. Either the system should cope with multiple identical tags, or it shouldn't allow you to make them.Principal of least astonishment. I guess you would have to cope with them, since you can't know that you've currently got the whole univer

Re: [Monotone-devel] Re: Best practice using monotone

"Andy Jones" <[EMAIL PROTECTED]> wrote: > Alternatively I could just write a script that did 'mtn update -r t:test' ! > > (Um, that +would+ get the +latest+ revision with that tag, right?) No. Tags are a different beast in Monotone. They are not mobile, for example. CVS's tag system was more

Re: [Monotone-devel] Re: Best practice using monotone

In message <[EMAIL PROTECTED]> on Thu, 24 Aug 2006 17:40:17 +0100, "Andy Jones" <[EMAIL PROTECTED]> said: andyjwork> Alternatively I could just write a script that did 'mtn update -r t:test' ! andyjwork> andyjwork> (Um, that +would+ get the +latest+ revision with that tag, right?) No, if there

[Monotone-devel] Re: Best practice using monotone

"Andy Jones" <[EMAIL PROTECTED]> writes: > In CVS I had a permanent work area sticky on the tag "test". As each > change was tested and passed by the QA team it got tagged. Then all I > had to do was "cvs update" in the release area. The unit test version > of the product ran from this working

Re: [Monotone-devel] Re: Best practice using monotone

In CVS I had a permanent work area sticky on the tag "test". As each change was tested and passed by the QA team it got tagged. Then all I had to do was "cvs update" in the release area. The unit test version of the product ran from this working area, expected the code to be there. It seems to

[Monotone-devel] Re: Best practice using monotone

"Andy Jones" <[EMAIL PROTECTED]> writes: [...] > I couldn't say whether the current model was a good one or not. The > testresult thing seems useful but not to me - in the language I use, > the only thing you could do with it would be to check that the > programs compiled, and any developer that

Re: [Monotone-devel] Re: Best practice using monotone

Entirely at right angles to it, I'm afraid.  But if it's not best practice to use it, I suppose that's all I need to know.I couldn't say whether the current model was a good one or not.  The testresult thing seems useful but not to me - in the language I use, the only thing you could do with it wou

[Monotone-devel] Re: Best practice using monotone

"Andy Jones" <[EMAIL PROTECTED]> writes: > Okay, only one more dumb question that I can think of: is there a doc > somewhere that explains how the trust / quality assurance model works? Just the manual, I think. And I don't think anyone really believes what's there works particularly well (in t