From: Jeff King <peff@peff.net>
To: "Morten W. J." <morten@winkler.dk>
Cc: git@vger.kernel.org
Subject: Re: Two consecutive clones of a remote produces different files
Date: Fri, 15 Jul 2016 05:42:01 -0400 [thread overview]
Message-ID: <20160715094200.GA17917@sigill.intra.peff.net> (raw)
In-Reply-To: <2183637.OVprKRVBmt@t430>
On Fri, Jul 15, 2016 at 10:45:47AM +0200, Morten W. J. wrote:
> I have a repository hosted on a GitLab server on my LAN and when I clone that
> repository to a linux box and a windows box I get different files!
>
> It is very hard to explain in words, so I have recorded my desktop while
> reproducing it, which I can do consistently:
>
> https://dl.dropboxusercontent.com/u/5234017/git-clone-produces-different-results.ogv
>
> I have no ideas what is wrong or why it behaves the way it does, but I am
> actually pretty scared now. The repository has been updated from as a subtree
> from another repository, but that should not create such behavior?
Just a blind guess, but might you have two files with names that differ
only in case, and on Windows one is overwriting the other because you
have a case-insensitive filesystem?
Try:
git ls-files -s | grep -i src/LogEventSubscriber.h
to see what is in the index (which is case-sensitive, and is the source
from which git checks the files out into the working tree).
-Peff
next prev parent reply other threads:[~2016-07-15 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 8:45 Two consecutive clones of a remote produces different files Morten W. J.
2016-07-15 9:42 ` Jeff King [this message]
2016-07-15 18:16 ` [SOLVED] " Morten W. J.
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=20160715094200.GA17917@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=morten@winkler.dk \
/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).