From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Odd, is it not? mkdir 'e:\' cannot be undone by rmdir 'e:\' ...
Date: Tue, 03 Sep 2019 08:40:00 -0000 [thread overview]
Message-ID: <dd6bf485b6fcfc461ba83ed6296376c3@smtp-cloud9.xs4all.net> (raw)
In-Reply-To: <20190902081508.GB4164@calimero.vinschen.de>
On Mon, 2 Sep 2019 10:15:08, Corinna Vinschen wrote:
>
> On Sep 1 19:38, Houder wrote:
> > Hi Corinna,
> >
> > My last post in this issue.
> >
> > As reported, Eric's code snippet in rmdir() (dir.cc) has become
> > redundant, lines 317 - 325 can be removed.
>
> This is what I'm not entirely sure about. There's some kind of
> bordercase and as soon as we release Cygwin with this change,
> as chance would have it somebody will report a problem.
And you would be correct ... :-P (see below)
> I'm not opposed to removing this code, but I'd like to get Eric's
> input on this.
Sure, I understand (Eric is far more knowledgable than I am).
Henri
-----
64-@@ uname -a
CYGWIN_NT-6.1 Seven 3.1.0 path.cc-!opt (2019-09-02 15:11 2019-09-02 15:11 x86_64 Cygwin
------------
That is, I am using an modified 3.1.0-0.2 ...
64-@@ mkdir aap
64-@@ ln -s aap noot
64-@@ mkdir noot
mkdir: cannot create directory ânootâ: File exists
64-@@ mkdir noot/
mkdir: cannot create directory ânoot/â: File exists
64-@@ rmdir aap
64-@@ mkdir noot
mkdir: cannot create directory ânootâ: File exists
64-@@ mkdir noot/ <==== Whao! So that is what Eric indicated in his commit!
64-@@ ls -ld aap <==== WRONG! WRONG!
drwxr-xr-x+ 1 Henri None 0 Sep 3 10:28 aap
Investigating ...
=====
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-09-03 8:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 15:25 Houder
2019-08-27 16:28 ` Corinna Vinschen
2019-08-27 17:01 ` Houder
2019-08-27 17:32 ` Vince Rice
2019-08-27 17:50 ` Corinna Vinschen
2019-08-28 7:16 ` Houder
2019-08-28 9:22 ` john doe
2019-08-28 11:47 ` Houder
2019-08-28 13:22 ` Corinna Vinschen
2019-08-28 14:16 ` Eric Blake
2019-08-28 14:22 ` Corinna Vinschen
2019-08-28 15:18 ` Corinna Vinschen
2019-08-29 15:19 ` Houder
2019-08-30 8:20 ` Corinna Vinschen
2019-08-30 12:42 ` Houder
2019-09-01 17:38 ` Houder
2019-09-02 8:15 ` Corinna Vinschen
2019-09-03 8:40 ` Houder [this message]
2019-09-03 6:50 ` Andrey Repin
2019-09-19 19:51 ` Ken Brown
2019-09-20 9:11 ` Houder
2019-09-20 18:20 ` Houder
2019-09-21 16:07 ` Ken Brown
2019-09-22 7:34 ` Houder
2019-09-22 14:12 ` Ken Brown
2019-09-07 3:47 ` L A Walsh
2019-08-27 19:48 ` Achim Gratz
2019-08-27 20:58 ` Brian Inglis
2019-08-28 7:16 ` Corinna Vinschen
2019-08-27 22:21 ` Achim Gratz
2019-08-28 13:36 ` Eric Blake
2019-08-28 22:57 ` Houder
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=dd6bf485b6fcfc461ba83ed6296376c3@smtp-cloud9.xs4all.net \
--to=houder@xs4all.nl \
--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).