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 839
    • Issues 839
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • 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
  • #998

Closed
Open
Created Jul 23, 2011 by Bitbucket Importer@bitbucket_importerOwner

record extention need be avail for commit\refreshpatch

Created originally on Bitbucket by Anonymous

try to use thg2.1.1 workbench to create new patch and rebuild current patch of MQ queue. in old thg1x that was intuitive record extention implemented and i`ve easy select\deselect hunks need in changeset. in new thg, as i understand, shelve extention shoud use to select hunks, but this is not capable to reconfigure current changeset\patch - cause hunks accepted in changeset is not viewable in working dir, and as for patches - shelve can rebuild only unapplyed patches, and this is real tricky to record a few patches from current working dir changes. I vote, imho it is realy need to come back record extention reatures from old thg1x into new workbench.

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