Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
thg
thg
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 797
    • Issues 797
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

This instance will be upgraded to the latest Heptapod 0.20rc on 2021-02-26 at 11:00 UTC+1

  • mercurial
  • TortoiseHg
  • thgthg
  • Issues
  • #393

Closed
Open
Opened Mar 19, 2011 by Bitbucket Importer@bitbucket_importerOwner

Updating repo with dirty subrepo is not safe

Created originally on Bitbucket by janrysavy

While updating dirty main repository with THG, there is following message displayed: "Confirm Update" / "Detected uncommitted local changes in working tree."

But I don't get this message when updating repository with dirty sub repository. Such subrepo is overwritten without single warning, ale uncommitted changes are lost.

It looks like same problem is in latest Mercurial. Any chance to make THG safer? For example run "hg status -S" before update? Should I put this problem to Mercurial tracker too?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: mercurial/tortoisehg/thg#393