From: "Jakub Narębski" <jnareb@gmail.com>
To: Jared Brank <jared.brank@skaletech.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git detects changes after new branch created and switched even though files have not been changed
Date: Wed, 06 Aug 2014 18:02:06 +0200 [thread overview]
Message-ID: <53E2517E.8020301@gmail.com> (raw)
In-Reply-To: <a2546f9109674431820b7a98f9570433@BL2PR05MB180.namprd05.prod.outlook.com>
W dniu 2014-08-06 17:04, Jared Brank pisze:
> Running on Windows with latest version of Git. 1.9.4. Also had this
> trouble with 1.8.2 but upgraded hoping it would fix the problem.
>
> When I do a reset on several files, it says they were successfully
> reverted they still show up as modified when I do a git status. In
> this case it's just a newline character at the end of the file.
The problem might be the options (gitconfig and gitattributes)
affecting how Git deals with end-of-line characters.
--
Jakub Narębski
prev parent reply other threads:[~2014-08-06 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 15:04 Git detects changes after new branch created and switched even though files have not been changed Jared Brank
2014-08-06 16:02 ` Jakub Narębski [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=53E2517E.8020301@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jared.brank@skaletech.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).