Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • mercurial-devel mercurial-devel
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Merge requests 30
    • Merge requests 30
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar

Due to a massive storm of spam, registration on this instance now requires explicit administrator approval. Sorry for the added friction, we're also looking into automatic filtering options.

  • mercurialmercurial
  • mercurial-develmercurial-devel
  • Merge requests
  • !159

rust-status: don't trigger dirstate v1 rewrite when only v2 data is changed

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Raphaël Gomès requested to merge topic/stable/rust-hg-purge into branch/stable Jun 08, 2022
  • Overview 3
  • Commits 1
  • Pipelines 2
  • Changes 3

The assumption that we need to rewrite (or append to) the dirstate if the ignore pattern hash has changed or if any cached directory mtimes have changed is only valid when using dirstate-v2. In dirstate-v1, neither of these things are written to disk.

Edited Jun 09, 2022 by Raphaël Gomès
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: topic/stable/rust-hg-purge