From: Jon Forrest <nobozo@gmail.com>
To: git@vger.kernel.org
Subject: Odd Difference Between Windows Git and Standard Git
Date: Thu, 19 May 2016 18:48:18 -0700 [thread overview]
Message-ID: <nhlqd4$ekr$1@ger.gmane.org> (raw)
I'm running Git version 2.8.2 built from source on Ubuntu 16.04.
I'm using a repository that's stored on Dropbox. I'm the only person
accessing this repo. Everything works great.
For reasons unrelated to Git, I decided to try Git for Windows,
so I installed "git version 2.8.2.windows.1" on Windows 10.
When I run 'git status' on Ubuntu the list I see is exactly what
I expect. However, when I run 'git status' on the
same Dropbox repo on Windows, I see what I expect plus I'm told
that every .pdf file and some .png files are modified.
I'm guessing that this is caused by some mishandling of
binary files. Is this behavior to be expected? If so, is there
something I can do to have the output on Windows be the
same as on Ubuntu? I'm aware of 'git update-index --assume-unchanged'
but this seems harsh.
I copied the repo to a non-Dropbox location, just in case
it was Dropbox that was causing the problem, but this didn't
make any difference.
(If you want to try this yourself, try it on the ProGit2
book source on Github).
Thanks,
Jon Forrest
next reply other threads:[~2016-05-20 1:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 1:48 Jon Forrest [this message]
2016-05-20 13:19 ` Odd Difference Between Windows Git and Standard Git Torsten Bögershausen
2016-05-20 13:48 ` Jon Forrest
2016-05-20 14:19 ` Torsten Bögershausen
2016-05-20 14:28 ` Jon Forrest
2016-05-20 15:57 ` Torsten Bögershausen
2016-05-20 15:23 ` Junio C Hamano
2016-05-20 16:12 ` Torsten Bögershausen
2016-05-20 16:21 ` Junio C Hamano
2016-05-23 11:12 ` Johannes Schindelin
2016-05-23 13:44 ` Jon Forrest
2016-05-23 15:08 ` Johannes Schindelin
2016-05-23 18:52 ` Junio C Hamano
2016-05-24 4:52 ` Torsten Bögershausen
2016-05-24 11:57 ` Johannes Schindelin
2016-05-25 4:36 ` Torsten Bögershausen
2016-05-25 11:52 ` Johannes Schindelin
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='nhlqd4$ekr$1@ger.gmane.org' \
--to=nobozo@gmail.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).