From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lars Magne Ingebrigtsen'" <larsi@gnus.org>
Cc: 6397@debbugs.gnu.org
Subject: bug#6397: 24.0.50; `make-directory' return value
Date: Wed, 13 Jul 2011 16:45:56 -0700 [thread overview]
Message-ID: <9D1FDD7C623F4C0BB2CAB12AB5B2EF30@us.oracle.com> (raw)
In-Reply-To: <m3wrflkbu1.fsf@quimbies.gnus.org>
> I don't think there's anything that can be done about that.
> Creating a full path isn't atomic,
We know we're trying to create a hierachy of directories, and we know that it
must be an all-or-nothing transaction. Why can't we make this atomic in this
particular case?
There's nothing magic about transactions. In this case the rollback would be
simple: delete any directories created if for some reason we cannot create them
all.
> and deleting the directories we've already made
> is bad, too.
Why? That's a normal rollback for this. There's not a lot going on here: just
directory creation.
> Some other process may have wanted the directories at the
> same time, and would bug out if we started deleting them.
I suppose that's a legitimate point in the abstract, but highly unlikely in
practice. And there is probably some way (file attributes? permissions?) of
making any created directories invisible/inaccessible during the transaction.
I don't see why Emacs Dev wouldn't try to fix this correctly. Unless I'm
missing something.
next prev parent reply other threads:[~2011-07-13 23:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 20:49 bug#6397: 24.0.50; `make-directory' return value Drew Adams
2010-06-11 8:12 ` Juri Linkov
2010-06-11 13:33 ` Drew Adams
2011-07-13 22:22 ` Lars Magne Ingebrigtsen
2011-07-13 22:47 ` Drew Adams
2011-07-13 23:19 ` Lars Magne Ingebrigtsen
2011-07-13 23:45 ` Drew Adams [this message]
2011-07-13 23:54 ` Lars Magne Ingebrigtsen
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=9D1FDD7C623F4C0BB2CAB12AB5B2EF30@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=6397@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.