> From: Fabrizio Cioni <fabrizio.ci...@gmail.com>
> I don't understand why the existing logic allows it, but i clearly see how 
> a distracted/in a rush/sleepless developer can make a mess of it; still 
> recoverable but very time-consuming when you find it x days later.

There is the converse problem of making a bunch of changes, and then
realizing that you don't have the correct branch checked out:  "git
checkout" changes the base branch and carries the changes to the
revised working copy.  Then you commit.

One answer to this problem is that you should always review your
changes just before committing them, to make sure that you are
checking in what you think you are checking in.


You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to