public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Git test failures if and only if Git worktree is outside /home
Date: Sat, 19 Dec 2020 19:36:52 +0100	[thread overview]
Message-ID: <87tush4p8b.fsf@Rainer.invalid> (raw)
In-Reply-To: <CA+kUOamhpjh=HUK7hhsmoiTgHSAoHmC9tgFNiOzUie0__wKFTQ@mail.gmail.com> (Adam Dinwoodie's message of "Sat, 19 Dec 2020 18:08:00 +0000")

Adam Dinwoodie writes:
> As part of testing the latest Git release candidate, I've spotted some
> behaviour I don't know where to begin explaining: one of the test
> scripts fails if my Git worktree is at, say, /cygdrive/c/git, but not
> if it's at /home/Adam/git.

I've already answered to your post on the Git mailing list.

> My suspicion is that Cygwin's behaviour is reasonable and this just
> isn't a valid test to run within a /cygdrive/ mountpoint, but that's
> based entirely on history of similar problems rather than any
> understanding of what's going on here. Can someone who has some vague
> understanding of the /cygdrive/ behaviour take a look and see if they
> can work out what's going wrong here?

No, there's something else going on in this case.  the only thing that
/cygdrive should do is to remove any pretenses of (or actual) case
sensitivity, via the posix=0 mount option that is the default for it.


Reghards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

      reply	other threads:[~2020-12-19 18:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19 18:08 Adam Dinwoodie
2020-12-19 18:36 ` Achim Gratz [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=87tush4p8b.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).