On 10/14/2016 12:13 AM, Peter Kronenberg wrote:
Thanks. Didn't realize that. How does one tell what is the 'top-level' way to do things? The documentation is somewhat sparse, to say the least.
We do not have an official internal API so there is not too much centralized doc about this. But we are slowly building one to help internal development.
The method I wanted to point you to is actually `repo.revs(…)` check that method documentation for details. This is the methods used by any internal piece of code that wants to run a revset.
If you input is user provided, have a look at: scmutil.revrange(repo, [revset_expression])
On Thu, Oct 13, 2016 at 6:10 PM, Pierre-Yves David <pierre-yves.da...@ens-lyon.org <mailto:pierre-yves.da...@ens-lyon.org>> wrote: On 10/13/2016 09:44 PM, Peter Kronenberg wrote: I have a server running 2.2.1 and I can't figure out the arguments for the result of revset.match In my 3.9.2 code, I have revsetQuery = ' ***query goes here*** ' revsetResult = revset.match(ui, revsetQuery) Any reasons you are using revset.match directly? The top level way to query a reset from a repository is `repo.set(your_query_goes_here)`. Now, I want to reference revsetResult(repo) or revsetResult(repo. None), both of which work in 3.9.2 But 2.2.1 doesn't like the second argument. It's supposed to be a subset, but not sure what to put if I don't want to specify a subset. -- Pierre-Yves David
-- Pierre-Yves David _______________________________________________ Mercurial-devel mailing list Mercurialfirstname.lastname@example.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel