On 02/28/14 09:41, Daniel Hunsaker wrote:
All that will happen is that any changes you've made to files git is tracking in the current commit will be reverted. New files will be left intact, as will ignored ones, but deleted files will be restored. Basically, checkout does its best to get you to the exact state described in the commit you specify, which in this case is the commit at the tip of master. If you haven't made any changes since the last checkout, it will do nothing at all.

Please correct me if I am wrong, but as far as I can tell using experimentation, checking out master while on master has no effect at all, regardless of whether files are changed, deleted, in the index or not.


On Fri, Feb 28, 2014 at 1:27 AM, dexter ietf <dexter.i...@gmail.com <mailto:dexter.i...@gmail.com>> wrote:

    i'm already on master branch, what's the effect of running the
    'git checkout master' while on master branch ?


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