git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Two consecutive clones of a remote produces different files

From
Jeff King <peff@peff.net>
Date
Jul 15, 2016, 09:42 UTC
Message-ID
<20160715094200.GA17917@sigill.intra.peff.net>
In-Reply-To
<2183637.OVprKRVBmt@t430>
On Fri, Jul 15, 2016 at 10:45:47AM +0200, Morten W. J. wrote:
Show 11 quoted lines
> 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
Previous: Morten W. J.Next: Morten W. J.
Message 2 of 3 in “Two consecutive clones of a remote produces different files”
  1. Morten W. J.Jul 15, 2016
  2. Jeff KingJul 15, 2016
  3. [SOLVED] Re: Two consecutive clones of a remote produces different filesMorten W. J., Jul 15, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.