From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55743@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
juri@linkov.net
Subject: bug#55743: 28.1.50; No directory error in comp-run-async-workers
Date: Fri, 03 Jun 2022 10:22:03 +0200 [thread overview]
Message-ID: <87y1yef978.fsf@igel.home> (raw)
In-Reply-To: <837d5ye1f0.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 03 Jun 2022 08:55:31 +0300")
On Jun 03 2022, Eli Zaretskii wrote:
> Yes, we can arrange for an existing directory, but:
>
> . it could be wrong, i.e. it could yield wrong compilation results
A remote directory would also be wrong.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-06-03 8:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 17:31 bug#55743: 28.1.50; No directory error in comp-run-async-workers Juri Linkov
2022-05-31 19:07 ` Eli Zaretskii
2022-05-31 19:49 ` Juri Linkov
2022-06-01 2:33 ` Eli Zaretskii
2022-06-01 6:13 ` Juri Linkov
2022-06-01 11:16 ` Eli Zaretskii
2022-06-01 19:13 ` Juri Linkov
2022-06-01 19:49 ` Eli Zaretskii
2022-06-02 7:40 ` Juri Linkov
2022-06-02 8:02 ` Eli Zaretskii
2022-06-02 8:17 ` Lars Ingebrigtsen
2022-06-02 8:44 ` Eli Zaretskii
2022-06-02 8:51 ` Lars Ingebrigtsen
2022-06-02 10:48 ` Eli Zaretskii
2022-06-03 3:10 ` Lars Ingebrigtsen
2022-06-03 5:55 ` Eli Zaretskii
2022-06-03 8:22 ` Andreas Schwab [this message]
2022-06-03 11:43 ` Eli Zaretskii
2022-06-02 8:17 ` Andreas Schwab
2022-06-02 8:45 ` Eli Zaretskii
2022-06-02 17:30 ` Juri Linkov
2022-06-02 19:02 ` Eli Zaretskii
2022-06-03 7:49 ` Juri Linkov
2022-06-03 11:12 ` Eli Zaretskii
2022-06-01 6:10 ` Juri Linkov
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=87y1yef978.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=55743@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--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.