From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>, Paul Eggert <eggert@cs.ucla.edu>
Cc: schwab@suse.de, bernardo.bacic@pobox.com, 37884@debbugs.gnu.org
Subject: bug#37884: 27.0.50; Cannot write to a file in VirtualBox shared directory
Date: Wed, 30 Oct 2019 18:25:31 +0200 [thread overview]
Message-ID: <831ruup5dw.fsf@gnu.org> (raw)
In-Reply-To: <m2k18mnyvh.fsf@gmail.com> (message from Robert Pluim on Wed, 30 Oct 2019 14:31:30 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: Andreas Schwab <schwab@suse.de>, 37884@debbugs.gnu.org, eliz@gnu.org
> Date: Wed, 30 Oct 2019 14:31:30 +0100
>
> >>>>> On Wed, 30 Oct 2019 19:44:35 +1100, Bernardo <bernardo.bacic@pobox.com> said:
> Bernardo> confirmed this patch works fine;
> Bernardo> thanks for the effort (and persistence)
>
> Thanks for testing. Eli, Andreas, let me know of any further issues,
> otherwise Iʼll push in the next couple of days.
Thanks. I'd like to hear Paul's opinion on this change. Paul, do you
see any downsides to the last change posted in this discussion? IOW,
could there be some situations where it could do any harm?
TIA
next prev parent reply other threads:[~2019-10-30 16:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 10:28 bug#37884: 27.0.50; Cannot write to a file in VirtualBox shared directory Bernardo
2019-10-24 16:10 ` Robert Pluim
[not found] ` <87blu2emi3.fsf@pobox.com>
2019-10-27 15:34 ` Robert Pluim
2019-10-27 15:52 ` Eli Zaretskii
2019-10-27 16:01 ` Robert Pluim
2019-10-27 16:34 ` Eli Zaretskii
2019-10-28 9:23 ` Bernardo
2019-10-28 12:32 ` Robert Pluim
2019-10-29 8:50 ` Bernardo
2019-10-29 9:04 ` Andreas Schwab
2019-10-29 13:41 ` Robert Pluim
2019-10-30 8:44 ` Bernardo
2019-10-30 13:31 ` Robert Pluim
2019-10-30 16:25 ` Eli Zaretskii [this message]
2019-10-31 1:41 ` Paul Eggert
2019-10-31 7:38 ` Robert Pluim
2019-10-31 14:37 ` Eli Zaretskii
2019-10-31 21:24 ` Paul Eggert
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=831ruup5dw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37884@debbugs.gnu.org \
--cc=bernardo.bacic@pobox.com \
--cc=eggert@cs.ucla.edu \
--cc=rpluim@gmail.com \
--cc=schwab@suse.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).