{"thread":{"id":"22951","subject":"Git status shows modifications after cloning","startedAt":"2010-03-08T15:32:25Z","lastAt":"2010-03-08T18:37:31Z","messageCount":3,"participants":["jateeq","Ilari Liusvaara"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"136393","messageId":"27821819.post@talk.nabble.com","threadId":"22951","inReplyTo":null,"subject":"Git status shows modifications after cloning","fromName":"jateeq","fromEmail":"jawad_atiq@hotmail.com","sentAt":"2010-03-08T15:32:25Z","receivedAt":"2010-03-08T15:32:25Z","isPatch":false,"sender":{"key":"jawad_atiq@hotmail.com","avatar":null},"body":"\nHello,\n\nAfter cloning from a local repository, a git status shows me that each file\nin the repository has been modified - I don't want this to happen. I have\nsearched around the net, and there is stuff about this happening if the\nconfigurations for the original and the clone are not the same, with\nspecific mention of the variable core.autocrlf. However, this variable is\nunspecified in both repositories, and the differences in config files is\nlisted below.\n\nOrigin:\n[core]\n\trepositoryformatversion = 0\n\tfilemode = true\n\tbare = true\n\nClone:\n[core]\n\trepositoryformatversion = 0\n\tfilemode = true\n\tbare = false\n\tlogallrefupdates = true\n[remote \"origin\"]\n\tfetch = +refs/heads/*:refs/remotes/origin/*\n\turl = /home/ruggeddoc/Documents/Primary/InstallationGuides/RuggedBackbone\n[branch \"master\"]\n\tremote = origin\n\tmerge = refs/heads/master\n[branch \"jateeq.2010-03-08.09-49\"]\n\tremote = origin\n\tmerge = refs/heads/master\n\nI haven't tried unsetting the logallrefupdates (I want to log updates). Does\nanyone think this is a config file issue? If it is, any idead on how to\nsolve it? If not, what can I do so that git status, or git diff do not show\nmodified files right after cloning?\n\nNOTE: On the origin, the only branch that exists is master, whereas after\nI'm done cloning, I create another branch and then checkout that branch's\nhead right from the start. \n\nThank you for your help, \nJawad\n-- \nView this message in context: http://old.nabble.com/Git-status-shows-modifications-after-cloning-tp27821819p27821819.html\nSent from the git mailing list archive at Nabble.com.\n"},{"id":"136394","messageId":"20100308154021.GA27413@Knoppix","threadId":"22951","inReplyTo":"27821819.post@talk.nabble.com","subject":"Re: Git status shows modifications after cloning","fromName":"Ilari Liusvaara","fromEmail":"ilari.liusvaara@elisanet.fi","sentAt":"2010-03-08T15:40:22Z","receivedAt":"2010-03-08T15:40:22Z","isPatch":false,"sender":{"key":"ilari.liusvaara@elisanet.fi","avatar":null},"body":"On Mon, Mar 08, 2010 at 07:32:25AM -0800, jateeq wrote:\n> \n> After cloning from a local repository, a git status shows me that each file\n> in the repository has been modified - I don't want this to happen. I have\n> searched around the net, and there is stuff about this happening if the\n> configurations for the original and the clone are not the same, with\n> specific mention of the variable core.autocrlf. However, this variable is\n> unspecified in both repositories, and the differences in config files is\n> listed below.\n\nAt least having core.autocrlf enabled and having CRLF files in repository\nis known to cause problems like that. But reading the configuration, it doesn't\nlook this is Windows system (and the rest don't tend to have core.autocrlf\nenabled).\n\nThe files in repository definitely should not have CRLF line endings (the\nproper one is just LF).\n\n-Ilari\n"},{"id":"136399","messageId":"27825623.post@talk.nabble.com","threadId":"22951","inReplyTo":"27821819.post@talk.nabble.com","subject":"Re: Git status shows modifications after cloning","fromName":"jateeq","fromEmail":"jawad_atiq@hotmail.com","sentAt":"2010-03-08T18:37:31Z","receivedAt":"2010-03-08T18:37:31Z","isPatch":false,"sender":{"key":"jawad_atiq@hotmail.com","avatar":null},"body":"\nI'm sorry i forgot to mention that I'm using Linux. Well, no, autocrlf wasn't\nset by default, but I still get all those modifications in the status. Any\nother reasons why this could be happening?\n\nJawad \n-- \nView this message in context: http://old.nabble.com/Git-status-shows-modifications-after-cloning-tp27821819p27825623.html\nSent from the git mailing list archive at Nabble.com.\n"}]}