#22104 closed enhancement (fixed)
mercurial-7.1.1
| Reported by: | Bruce Dubbs | Owned by: | Bruce Dubbs |
|---|---|---|---|
| Priority: | normal | Milestone: | 13.0 |
| Component: | BOOK | Version: | git |
| Severity: | medium | Keywords: | |
| Cc: |
Description
New point version.
Change History (4)
comment:1 by , 12 months ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 12 months ago
comment:3 by , 12 months ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Fixed at commit 4d47d40b7b.
Note:
See TracTickets
for help on using tickets.

Mercurial 7.1.1 (2025-09-10)
A scheduled minor release containing only one series that is relevant for these notes.
The series fixes the way we detect non-critical repository corruption due to issue6528 because, unfortunately, the fix for issue6528 was itself buggy.
This means that if your repo had the on-the-fly rewrite option on (which is the default), too many file revisions will have been marked as having metadata, potentially costing you a bit of performance because Mercurial will look for metadata that isn't there.
Your repository will behave completely fine by not doing anything, and we even have work well underway that changes how we flag file revisions with metadata, removing the root of this problem entirely.
If you want to fix this however, as with the original issue, this problem is contagious across the wire so you need to first upgrade to 7.1.1 to get the correct on-the-fly rewrite, and then run the
hg debug-repair-issue6528command to repair your clone. Consult the help of this command for more options.