From: "Morten W. J." <morten@winkler.dk>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: [SOLVED] Re: Two consecutive clones of a remote produces different files
Date: Fri, 15 Jul 2016 20:16:00 +0200 [thread overview]
Message-ID: <3779136.PWlxYSPs5e@t430> (raw)
In-Reply-To: <20160715094200.GA17917@sigill.intra.peff.net>
Hi Jeff.
Hmmm. You are the master of blind guessing - spot on.
Also, that is kind of embaressing to me. However, should your way cross mine,
you hereby have a voucer for a drink after your choice as long as it is beer.
Thanks,
Morten.
> 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
prev parent reply other threads:[~2016-07-15 18:32 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
2016-07-15 18:16 ` Morten W. J. [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=3779136.PWlxYSPs5e@t430 \
--to=morten@winkler.dk \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).