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
  • #19
Closed
Open
Issue created Oct 18, 2010 by Bitbucket Importer@bitbucket_importerOwner

Sub-repos marked dirty when they aren't. Sometimes leads to empty changeset

Created originally on Bitbucket by Anonymous

I am using mercurial 1.6.4 and TortoiseHG 1.1.4. When I do a commit on a master repo it sometimes shows some of the sub-repos as dirty, even though there are no changes in them.

In one case it just checked in an empty changeset in only one of the three sub-repos that it indicated were dirty and thus triggred a change to the .hgsubstate file in the master as well. The funny thing is that THG claimed "No changes" when we told it to comming, yet checking the repo history it is clear that an empty changeset was created.

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