Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • thg thg
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 838
    • Issues 838
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mercurialmercurial
  • TortoiseHgTortoiseHg
  • thgthg
  • Issues
  • #3952
Closed
Open
Issue created Oct 26, 2014 by Bitbucket Importer@bitbucket_importerOwner

can't commit subrepos after rolling back

Created originally on Bitbucket by dddinu (Dinu M)

When rolling back a commit that involves subrepos, the subrepos'cursors are not rewinded to the state prior the commit. I assume this is a hg bug.

What seems to be a tortoise bug however is this: when trying to commit again, .hgsubstate is listed in the commit files list, but is not committed. .hgsubstate is still listed as modified but a new commit attempt promts that nothing's changed. The only way to re-commit a rolled back commit with subrepos is to revert .hgsubstate after the rollback. Then tortoise identifies the changed subrepo state appropriately and everything works again.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking