Suppose, hypothetically speaking, one were a long time user of CVS who converted to subversion in the last 18 months or so, and who never really understood branches and merging because the syntax was so obtuse and because the projects this hypothetical person had worked were short lived enough that (s)he never really needed to create a branch. Now suppose this hypothetical person was working on a new project, decided to use git as the project's version control system, got halfway through changing a bunch of files, wanted to commit them as they were, since they worked, but were ugly as sin, and wanted to clean them up before committing them back to the main line of development. I would tell that hypothetical person, "Gee, it sounds like a branch is exactly what you need here". Unfortunately I don't know how to tell the person to do the equivalent of a "svn switch" when the local repository has been modified. $ git branch newbranch that works, but $ git checkout newbranch complains that an untracked file would be overwritten by the merge (since one of the things that this hypothetical person may have done would have been to do a "git mv somefile someotherfile"). What would you suggest I say to this person other than "get in the habit of creating a new branch _any_ time you start something new". --wpd - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
