On Wed, Oct 5, 2011 at 9:15 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Jay Soffian <jaysoffian@xxxxxxxxx> writes: > >> So you're envisioning this? >> >> $ git commit foo.c >> Warning, master is also checked out in workdir2 > > No. I would rather think it needs to be forced. Now they do what? Either commit --force or create a new branch? Wouldn't it have been better to create the new branch before they started editing? Here's what I'm trying to avoid: $ cd workdir2 $ git checkout master $ edit foo.c $ git commit foo.c By default, committing to a branch that is checked out in more than one location is denied, because it will make the index and work tree inconsistent in the other locations and will require 'git reset --hard' to match the work tree to HEAD in each of those other locations. Either switch to a new branch first with 'git checkout -b <new_branch>' or use 'git commit --force' to override this message. User: "crap, I wanted that on master". Now they do what. Something like: $ git checkout -b foo $ git commit foo.c $ cd workdir1 $ git cherry-pick foo $ git branch -d foo Or maybe they use stash instead. In either case, I just think that's a terrible user experience compared to: $ cd workdir2 $ git checkout master error: master already checked out in workdir1 $ cd workdir1 $ edit foo.c $ git commit foo.c I guess it depends what you mostly use your workdirs for. For me, it's to have different branches checked out, not to have the same branch checked out in multiple locations. I want git to help me up front, not when I go to commit. j. -- 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