> If there is no conflicting changes all of your current changes will be kept > but you'll now be working in the new branch.
That's exactly the problem, because this is hardly ever what I want. The solution seems to be to commit prematurely, or stash into a stack where you lose track which branch a given stash came from. - Gordon -----Original Message----- From: Justin Mclean [mailto:jus...@classsoftware.com] Sent: Tuesday, March 19, 2013 4:16 PM To: dev@flex.apache.org Subject: Re: Git's "branches are cheap and fast but modal" model Hi, > When you work on a branch, and you want to work on another branch, you first > have to commit in the current branch you working on to save your work. Git checkout branch is not quite the same as switching branches in SVN. If there is no conflicting changes all of your current changes will be kept but you'll now be working in the new branch. You may need to be careful with this as it's possible to commit changes form one branch into another accidentally. Justin
