On 08/31/2011 11:24 AM, in-git-vger@xxxxxxxx wrote: > > In message <sDZ5pnWzh3ZbFYS6GK-NcPdn09kF53MJ2eRkBnzInzdL8-cvCiF5beUw2k9Pz6BTq-Y3i_XwpYfgTOvXNlP1vPjLSHJ6FIzxL0jN1W0d0M8@xxxxxxxxxxxxxxxxxxxxxx>, Brandon Casey writes: > > rm -rf * && # remove the files in the working dir > > I just note (for your information only) that this doesn't get rid of > any . files which might exist. That is the advantage of the > git-read-tree;git-clean or the `find | xargs rm` alternatives I > mentioned in my post. 99% of the time it doesn't matter of course, > since it would only fail on . files which were deleted in the data > stream you were replacing. I was just crafting a reply to your message to say the same thing. Note also that the dot files would not have been copied into the working directory in the first place, using a command like this: cp -a /some/path/* . So, Ryan, if your project contains dot files that you would want to track, take care that they are actually copied and deleted with the other files while you are creating your repository. -Brandon -- 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