Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
TortoiseGit
TortoiseGit
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 304
    • Issues 304
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 9
    • Merge requests 9
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TortoiseGit
  • TortoiseGitTortoiseGit
  • Issues
  • #1443

Closed
Open
Created Aug 02, 2015 by Sven Strickroth@mrtuxOwner

git svn dcommit: unclear behavior for dirty working tree

By robert.pol... on October 10, 2012 12:41 (imported from Google Code)


What steps will reproduce the problem?

  1. use TortoiseGit as SVN client
  2. try dcommit with a dirty working tree

This gives a dialog:
> Current working tree is not clear
> Do you want to stash change?
> [Yes] [No]

This dialog should describe what will happen with my uncommitted changes when I click "No". Are they lost?

(using TortoiseGit-1.7.13.0-64bit)

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