From: Ken Brown <kbrown@cornell.edu>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 32246@debbugs.gnu.org
Subject: bug#32246: 27.0.50; files-tests failure on Cygwin
Date: Fri, 27 Jul 2018 16:30:56 -0400 [thread overview]
Message-ID: <d50dfe60-e8a6-1284-4f6c-2aa1743bba46@cornell.edu> (raw)
In-Reply-To: <871sboqxwv.fsf@gmx.de>
On 7/27/2018 3:30 PM, Michael Albinus wrote:
Hi Michael,
> LGTM.
>
> I cannot build for cygwin myself. So if this patch fixes the error for
> you, you might commit.
Yes, it fixes the error. But I'll wait for Eli's approval before
committing.
> There's the other proposal from Eli, use the root of the volume. This
> would work also, but I don't know how to find the root of a volume
> easily.
I don't either. And this would be especially tricky on Cygwin, where
I'm not even sure what "volume" should mean. For example, /proc and
/cygdrive are case-insensitive on my system, even though I've set my
system up to be case-sensitive otherwise. So it seems that /proc and
/cygdrive should be viewed as separate file systems.
Best regards,
Ken
next prev parent reply other threads:[~2018-07-27 20:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-22 18:10 bug#32246: 27.0.50; files-tests failure on Cygwin Ken Brown
2018-07-22 18:23 ` Michael Albinus
2018-07-23 17:01 ` Ken Brown
2018-07-25 12:00 ` Michael Albinus
2018-07-25 13:37 ` Ken Brown
2018-07-25 16:46 ` Michael Albinus
2018-07-25 16:56 ` Ken Brown
2018-07-25 17:33 ` Michael Albinus
2018-07-26 13:56 ` Michael Albinus
2018-07-26 14:54 ` Ken Brown
2018-07-26 15:03 ` Michael Albinus
2018-07-27 18:34 ` Ken Brown
2018-07-27 19:30 ` Michael Albinus
2018-07-27 20:30 ` Ken Brown [this message]
2018-07-27 21:10 ` Eli Zaretskii
2018-07-27 21:32 ` Ken Brown
2018-07-27 21:34 ` Ken Brown
2018-07-26 17:38 ` Eli Zaretskii
2018-07-27 15:27 ` Michael Albinus
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d50dfe60-e8a6-1284-4f6c-2aa1743bba46@cornell.edu \
--to=kbrown@cornell.edu \
--cc=32246@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).