On Mon, Feb 22, 2016 at 12:22 AM, Matthieu Moy <matthieu....@grenoble-inp.fr> wrote: > Mehul Jain <mehul.jain2...@gmail.com> writes: > >> Earlier when I was testing the master branch on my pc, I used "make" >> in \t directory, which lead to failure of test #2, #3 in >> t5539-fetch-http-shallow.sh . >> Afterwards I switched to sudo mode and ran the make command again. > > Never ever do that. Your git source tree should be within your $HOME > directory, and you should never run any command as root that creates > files within your $HOME dir. If you do that, you'll end up having files > belonging to root within other directories, you won't have write > permission on these files. Then, anything can go wrong because any > attempt to write to these files will fail. > > The simplest way to get back on track for you is probably to start over > with a fresh clone, or (warning: destructive operations): use git clean > to remove untracked files. >
I think a 'sudo git clean' outta be enough. But the main point to take away is not using 'make' with 'sudo' like you mentioned. -- Regards, Karthik Nayak -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
