public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Please test latest developer snapshot
Date: Mon, 21 Feb 2011 15:21:00 -0000	[thread overview]
Message-ID: <4D6282CF.1000606@towo.net> (raw)
In-Reply-To: <4D6273C4.9050406@redhat.com>

Am 21.02.2011 15:16, schrieb Eric Blake:
> On 02/19/2011 11:29 AM, Warren Young wrote:
>   
>> On 2/17/2011 5:04 AM, Corinna Vinschen wrote:
>>     
>>> - Reintroduce the ability to delete an empty directory which is the
>>>    current working directory of the same or another Cygwin process.
>>>       
>> I don't see that.  Testcase:
>>
>>     $ mkdir foo
>>     $ cd foo
>>     $ rmdir .
>>     rmdir: failed to remove `.': Invalid argument
>>     
> POSIX doesn't allow rmdir(2) to succeed if the last component is '.'.
> You have to use rmdir ../foo instead.
>   
And this is not an artificial limitation but there is no way that this
could conceivably work.
By Unix design, removing a file or directory basically means removing
its entry from its parent directory, so it is not an operation on the
file in the first place (or on the target directory in this case).
The parent directory is obviously needed by design, thus "." is not
something that could ever be removed (from where?).
Thomas

--
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

  reply	other threads:[~2011-02-21 15:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 12:04 Corinna Vinschen
2011-02-17 18:06 ` Ken Brown
2011-02-17 18:15 ` marco atzeri
2011-02-18 12:36   ` Corinna Vinschen
2011-02-18 13:34     ` marco atzeri
2011-02-17 19:33 ` Aaron Peromsik
2011-02-17 20:15 ` Yaakov (Cygwin/X)
2011-02-19 18:29 ` Warren Young
2011-02-19 18:35   ` Warren Young
2011-02-19 20:35     ` Warren Young
2011-02-20 12:16       ` Corinna Vinschen
2011-02-21 14:16   ` Eric Blake
2011-02-21 15:21     ` Thomas Wolff [this message]
2011-02-26  0:25       ` Vorfeed Canal
2011-02-26  0:45         ` Eric Blake
2011-02-26  1:03         ` Thomas Wolff
2011-02-27  7:35           ` Vorfeed Canal
2011-02-27 10:21             ` Vorfeed Canal
2011-02-27 11:21             ` Vorfeed Canal
2011-02-24 14:57 ` Chris Sutcliffe
2011-02-24 15:16   ` Corinna Vinschen
2011-02-24 19:34     ` Karl M
2011-02-24 20:56       ` Reini Urban
2011-02-24 21:52 ` Kai Tietz
2011-02-25  9:47   ` Corinna Vinschen
2011-02-25 23:25 ` David Rothenberger
2011-02-26  0:09   ` David Rothenberger
2011-02-26  9:51     ` marco atzeri
2011-02-26 10:36     ` Corinna Vinschen
2011-02-27 14:15       ` Corinna Vinschen
2011-02-27 18:45         ` David Rothenberger
2011-03-01  7:06     ` Christopher Faylor
2011-03-01 15:51       ` David Rothenberger
2011-02-18 15:34 Angelo Graziosi
2011-02-19 16:05 ` jdzstz - gmail dot com
2011-02-27 15:03 Angelo Graziosi
     [not found] <AANLkTim4xT_LL=CGFXhgKmO0gLd5P_rXctaMpHwT2pxn@mail.gmail.com>
2011-03-03 12:22 ` Oleg Marchuk
2011-03-03 12:53   ` Oleg Marchuk
2011-03-03 16:41     ` Christopher Faylor

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=4D6282CF.1000606@towo.net \
    --to=towo@towo.net \
    --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).