Skip to content
GitLab
  • Menu
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 829
    • Issues 829
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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
  • mercurial
  • TortoiseHg
  • thgthg
  • Issues
  • #4319
Closed
Open
Created Oct 07, 2015 by Bitbucket Importer@bitbucket_importerOwner

Bisect dialog good/bad revision input validation is too strict (blocks syntaxes that plain hg accepts)

Created originally on Bitbucket by gstefanik (Gábor Stefanik)

THg's Bisect dialog overzealously validates the entered good/bad revisions, rejecting valid inputs for "hg bisect -g" and "hg bisect -b".

E.g. "hg bisect -g ancestor(0)" is valid and will mark the revision 0 as good (ancestor(0) is synonymous with 0), but entering ancestor(0) in the GUI Bisect dialog produces "unknown revision 'ancestor(0)'". This is a silly example, but someone may likewise want to use a date() predicate to specify a revision, which works on the console, but not in the GUI.

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