In hgweb log and graph views have a limit on the amount of revisions displayed at once. But this limit is calculated in an incorrect (at least from a user point of view) way: by the revision numbers instead of their actual amount. This causes displaying only few last revisions, if other (not hidden) ones have numbers which differ a lot: i.e. if you have revisions with numbers 1,2,3,1000,1001, then by default you will see only the last two of them.
I can't reproduce this on the log view, but I just mailed a patch for the graph view.
Fixed by http://selenic.com/repo/hg/rev/002b711a3e8a Alexander Plavin <me@aplavin.ru> hgweb: fix incorrect way to count revisions in log (issue3977) Actual amount of revisions is used now instead of their numbers in the repo before to deal with skipped numbers correctly. This iterates starting from the newest revision (which is shown on top) yielding up to the specified count, instead of the reversed order used before. Effect of this change on efficiency is negligible, when the same changesets are returned. (please test the fix)
Fixed by http://selenic.com/repo/hg/rev/8cfa3a3664a5 Alexander Plavin <me@aplavin.ru> hgweb: fix incorrect revisions count in graph (issue3977) Actual amount of revisions is used now instead of their numbers in the repo before to deal with skipped numbers correctly. (please test the fix)