From: Eli Zaretskii <eliz@gnu.org>
To: 19963@debbugs.gnu.org, kaushal.modi@gmail.com
Subject: bug#19963: 25.0.50; Unable to create a directory with name same as an existing file
Date: Fri, 27 Feb 2015 23:50:53 +0200 [thread overview]
Message-ID: <83twy73txe.fsf@gnu.org> (raw)
In-Reply-To: <83vbin3u0k.fsf@gnu.org>
> Date: Fri, 27 Feb 2015 23:48:59 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 19963-done@debbugs.gnu.org
>
> A directory is just a special kind of file on most filesystems, and
> like a file, it has an entry in its parent directory. So there cannot
> be a file and a directory with the same name, because there can be 2
> identical entries in their parent directory. ^^^^^^
I meant "cannot be", of course. Sorry.
prev parent reply other threads:[~2015-02-27 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 19:56 bug#19963: 25.0.50; Unable to create a directory with name same as an existing file Kaushal
2015-02-27 21:48 ` Eli Zaretskii
2015-02-27 21:50 ` Eli Zaretskii [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
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=83twy73txe.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19963@debbugs.gnu.org \
--cc=kaushal.modi@gmail.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.
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).