view CONTRIBUTING @ 49510:e02dcc625171

revset: handle wdir() in `roots()`

This is already handled in `heads()`, and both are needed to determine if a set
is contiguous.

I'm guessing the `0 <= p` check was to try to filter out the null revision, but
it looks like that comes through in the corner case of a new repo with no
commits.  But that was already the case, as shown by the tests.

Before (on a clone of hg):

    $ python3.8 hg perf::revset --config extensions.perf=contrib/perf.py 'roots(all())'
    ! wall 0.059301 comb 0.040000 user 0.040000 sys 0.000000 (best of 100)

After:

    $ python3.8 hg perf::revset --config extensions.perf=contrib/perf.py 'roots(all())'
    ! wall 0.059387 comb 0.060000 user 0.060000 sys 0.000000 (best of 100)

Our full contribution guidelines are in our wiki, please see:

https://www.mercurial-scm.org/wiki/ContributingChanges

If you just want a checklist to follow, you can go straight to

https://www.mercurial-scm.org/wiki/ContributingChanges#Submission_checklist

If you can't run the entire testsuite for some reason (it can be
difficult on Windows), please at least run `contrib/check-code.py` on
any files you've modified and run `python contrib/check-commit` on any
commits you've made (for example, `python contrib/check-commit
273ce12ad8f1` will report some style violations on a very old commit).