From: jateeq <jawad_atiq@hotmail.com>
To: git@vger.kernel.org
Subject: Git status shows modifications after cloning
Date: Mon, 8 Mar 2010 07:32:25 -0800 (PST) [thread overview]
Message-ID: <27821819.post@talk.nabble.com> (raw)
Hello,
After cloning from a local repository, a git status shows me that each file
in the repository has been modified - I don't want this to happen. I have
searched around the net, and there is stuff about this happening if the
configurations for the original and the clone are not the same, with
specific mention of the variable core.autocrlf. However, this variable is
unspecified in both repositories, and the differences in config files is
listed below.
Origin:
[core]
repositoryformatversion = 0
filemode = true
bare = true
Clone:
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = /home/ruggeddoc/Documents/Primary/InstallationGuides/RuggedBackbone
[branch "master"]
remote = origin
merge = refs/heads/master
[branch "jateeq.2010-03-08.09-49"]
remote = origin
merge = refs/heads/master
I haven't tried unsetting the logallrefupdates (I want to log updates). Does
anyone think this is a config file issue? If it is, any idead on how to
solve it? If not, what can I do so that git status, or git diff do not show
modified files right after cloning?
NOTE: On the origin, the only branch that exists is master, whereas after
I'm done cloning, I create another branch and then checkout that branch's
head right from the start.
Thank you for your help,
Jawad
--
View this message in context: http://old.nabble.com/Git-status-shows-modifications-after-cloning-tp27821819p27821819.html
Sent from the git mailing list archive at Nabble.com.
next reply other threads:[~2010-03-08 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 15:32 jateeq [this message]
2010-03-08 15:40 ` Git status shows modifications after cloning Ilari Liusvaara
2010-03-08 18:37 ` jateeq
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27821819.post@talk.nabble.com \
--to=jawad_atiq@hotmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).