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

[Emile Snyder]

On Thu, 2005-04-21 at 15:39, Nathaniel Smith wrote:
> Random idea: adding an "h:" selector, meaning "head", is on the todo
> list (I think someone was working on it?).  Could make the selector
> syntax recursive, so h:a:richard means "head of the set of revisions
> specified by a:richard", i.e., the latest.
> 
> This is probably a terrible idea, though, because then people will
> want a way to distinguish between h:(a:richard/b:net.venge.monotone)
> type parsing and (h:a:richard)/b:net.venge.monotone type parsing.

but don't h:(a:richard/b:net.venge.monotone) and
(h:a:richard)/b:net.venge.monotone mean the same thing (aren't they all
getting ANDed together?)

> > But as a separate issue, is there anything that we would want the
> > --cert=certname:certvalue flag that works like the --branch flag (in
> > fact, --branch would just be a special case, --cert=branch:branchname)
> > for?  Or am I just inventing useless features?
> 
> I don't see this as particularly useful.  --branch is not used to
> restrict to a given branch, primarily; why it's special is that it's
> used to determine, e.g., what sort of branch certs monotone _issues_,
> what branch monotone should default to when it needs to set a branch
> on a new working copy, that sort of thing.  There are some places like
> "heads" and "update" that use it in a restrictiony kind of way, but
> these seem to be special cases, not the main idea...

Point taken.

> It seems like what you want would be better implemented as a
> c:certname=certvalue selector?  That's been proposed on the list
> before, even, just nothing ever happened.

True, c: selector seems like a good thing to have.

thanks,
-emile

> -- Nathaniel

+----------------------------------------------------------------------
My name is sendmail.cf. You killed my process. Prepare to vi. 
+----------------------------------------------------------------------