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 799
    • Issues 799
    • 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
  • mercurial
  • TortoiseHg
  • thgthg
  • Wiki
  • BugReport

Last edited by sborho May 09, 2015
Page history

BugReport

Table of Contents

  • Report Bugs
    • Make sure the bug hasn't already been reported
    • Make sure you don't have incompatible third-party extensions
    • Creating a new issue
      • Traceback text
      • Writing precise steps to reproduce
      • Issue assignee to tortoisehg

Report Bugs

//Do not "Create page" to report bugs. Use issue tracker.//

Note: the Python bindings for subversion were deliberately removed from the TortoiseHg packages in release 3.4 for security and packaging reasons. They must be downloaded and setup manually if you need TortoiseHg to interact with subversion repositories. See libsvn

Make sure the bug hasn't already been reported

The first step should be to consult the list of **FixedBugs** that are already fixed on the tip of the stable branch, and are likely already in the nightly builds.

Also consult the open bug list.

Make sure you don't have incompatible third-party extensions

In general, you'll need to **upgrade hgsubversion, hggit** etc. at each major release, or switch to our packaged versions of those extensions.

Creating a new issue

If your bug is truly new, or if you have an idea for an enhancement,

    • report it to our issue tracker**.

Traceback text

The bug report dialog has a **Copy** button that copies the bug text to the clipboard. Simply paste the report into the entry form. If the bug report is more than a screen full of text, feel free to save it from the dialog and attach it to the new issue.

Writing precise steps to reproduce

If you remember what you were doing at the time the bug occurred, please add this to the bug report, as this is frequently much more important than the stack trace itself.

Issue assignee to tortoisehg

Please leave new issues assigned to the 'tortoisehg' user as this ensures emails for the issue are distributed to the appropriate mailing list.


See our **developers** wiki for details on contributing patches or other work.

Clone repository
  • BugReport
  • CentOS
  • FixedBugs
  • Home
  • KeySequences
  • Nit
  • OldNews
  • OlderReleaseNotes
  • OpenAtLine
  • ReleaseNotes
  • RoadMap
  • SVN HG
  • SVN
  • Ubuntu
  • developers
    • CommonSignals
View All Pages