view CONTRIBUTING @ 43961:a447efd991b9

verify: update comment to say that lfs doesn't need fulltext to check renames

The reason is that `filelog.renamed()` indirectly calls `filelog.revision()`,
which is what accesses the full text.  However, LFS wraps `filelog.renamed()`
and completely handles the case where an LFS blob is in play by using rawdata.

I've got a test to demonstrate that this is the case, and prevent regressions.
But the `skipread` flag is set on all lfs revisions when using `--no-lfs`,
regardless of whether or not the blobs are local.  Just above this, that flag is
consulted, causing the rename checks to be skipped.  That will need to be
loosened up first.

Differential Revision: https://phab.mercurial-scm.org/D7709

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).