From: Holger Hellmuth <hellmuth@ira.uka.de>
To: Ron Eggler <ron.eggler@gmail.com>
Cc: Andrew Ardill <andrew.ardill@gmail.com>, git@vger.kernel.org
Subject: Re: found some code...
Date: Wed, 18 Jan 2012 23:45:52 +0100 [thread overview]
Message-ID: <4F174BA0.2040109@ira.uka.de> (raw)
In-Reply-To: <CAHxBh_QiZzJP2jS6rMpC1c=P8uXSbFWumbcnHj3ArkQB4sXyPQ@mail.gmail.com>
Mmh, your reply here didn't make it to the mailing list, maybe because
it was multipart with html(??) or it just got lost.
Am 18.01.2012 18:57, schrieb Ron Eggler:
> Try "git update-index --refresh", more info in this recent thread
> "http://comments.gmane.org/__gmane.comp.version-control.__git/188291
> <http://comments.gmane.org/gmane.comp.version-control.git/188291>"
>
>
> I got this outputand nothing really changed(generally using TortoiseGit
> on Windows but did this in the provided bash shell):
> $ git update-index --refresh
> MCU2.COF.txt: needs update
> MCU2.bak: needs update
> MCU2.c: needs update
> MCU2.esym: needs update
> MCU2.h: needs update
> MCU2.hex: needs update
> MCU2.lst: needs update
> MCU2.mcp: needs update
[...]
Ok, "needs update" seems to be the non-porcelain version of 'M' (why 'M'
is more porcelain than "needs update" is a mystery to me ;-) respective
"Changes not staged for commit" in git status.
Well, what does it say when you do "git diff MCU2.h" ? There are 2
possibilities:
1) You see code differences. In that case you should be able to
recognize where and when these changes were comitted or not.
2) You see no difference or every line is listed as different even
though they seem to be equal. Possible reason is a mixup of line endings
as git on windows has to convert \r\n line endings to \n line endings
when it checks data in. This is controlled by config variables, and
maybe your config is slightly wrong.
In that case I would create a new repo with git init in bash (not
tortoise git!), and look at .git/config. Compare that with .git/config
of your mixed up repo. Also compare with .git/config of the repo on your
usb stick. As far as I know you should have core.autocrlf set to true on
Windows.
Alternatively or for a complete picture you could do "git config -l"
which gives you also global and system configuration variables if they
exist.
Another possible reason would be file names with same name but different
case. I mention this because there is a parallel thread on this mailing
list with a problem with tortoise git and windows. See
http://git.661346.n2.nabble.com/Bug-Git-checkout-fails-with-a-wrong-error-message-td7181244.html.
As suggested in that thread you should have the option core.ignorecase set.
> Ok ,let's see:
> I "found" the piece of code on my thumbdrive and it ultimately is copied
> from my "old" working directory from the computer i don't have
> anymore... "get create new local folders" means that I actually created
> a new folder on my new machine and cloned the repo from git into it so
> this would be my new working directory... now i have the code that
> should be in there seperatetely in the directory from the thumb drive....
> Does that make any more ssense?
>
prev parent reply other threads:[~2012-01-18 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 1:02 found some code Ron Eggler
2012-01-18 1:16 ` Andrew Ardill
2012-01-18 2:49 ` Ron Eggler
2012-01-18 9:56 ` Holger Hellmuth
[not found] ` <CAHxBh_QiZzJP2jS6rMpC1c=P8uXSbFWumbcnHj3ArkQB4sXyPQ@mail.gmail.com>
2012-01-18 22:45 ` Holger Hellmuth [this message]
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=4F174BA0.2040109@ira.uka.de \
--to=hellmuth@ira.uka.de \
--cc=andrew.ardill@gmail.com \
--cc=git@vger.kernel.org \
--cc=ron.eggler@gmail.com \
/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).