From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>,
"Nigko Yerden" <nigko.yerden@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: 72867@debbugs.gnu.org
Subject: [bug#72867] when should local-file and current-source-directory not follow symlinks?
Date: Sun, 01 Sep 2024 16:13:53 +0200 [thread overview]
Message-ID: <87a5grihr2.fsf@nckx> (raw)
In-Reply-To: <87v7zg1uvm.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Sat, 31 Aug 2024 19:10:05 +0200")
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
Hi,
pelzflorian (Florian Pelz) 写道:
> If we ignored possible custom code breakage, this patch could be
> simplified
Please consider doing so, responsibly[0], if everyone agrees that
the current default is suboptimal.
Keeping ossified (and unintentional?) quirks around forever has a
cost each time someone gets bitten by unintuitive behaviour. It
gets less recognition than, but eventually outweighs, any
immediate switching costs to out-of-tree users.
(…/me quietly eyes substitute*…)
Kind regards,
T G-R
[0]: With a news entry, for example.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2024-09-01 14:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 6:06 [bug#72867] [PATCH] gexp: Make 'local-file' follow symlinks Nigko Yerden
2024-08-29 7:01 ` [bug#72867] when should local-file and current-source-directory not follow symlinks? Attila Lendvai
2024-08-29 9:00 ` [bug#72867] [PATCH] gexp: Make 'local-file' follow symlinks Ludovic Courtès
2024-08-29 10:10 ` pelzflorian (Florian Pelz)
2024-08-30 12:07 ` Nigko Yerden
2024-08-30 14:00 ` [bug#72867] when should local-file and current-source-directory not follow symlinks? Nigko Yerden
2024-08-31 17:10 ` pelzflorian (Florian Pelz)
2024-09-01 14:13 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2024-09-02 4:41 ` [bug#72867] [PATCH v2] gexp: Make 'local-file' follow symlinks Nigko Yerden
2024-09-02 7:53 ` [bug#72867] [PATCH v3] " Nigko Yerden
2024-09-03 15:05 ` pelzflorian (Florian Pelz)
2024-09-05 5:06 ` Nigko Yerden
2024-09-05 4:16 ` [bug#72867] [PATCH v4] " Nigko Yerden
2024-09-06 4:17 ` [bug#72867] [PATCH v5] " Nigko Yerden
2024-09-07 7:35 ` pelzflorian (Florian Pelz)
2024-09-25 5:16 ` pelzflorian (Florian Pelz)
2024-09-26 7:07 ` [bug#72867] [PATCH v6] " Nigko Yerden via Guix-patches
2024-10-02 16:15 ` Ludovic Courtès
2024-10-03 13:22 ` pelzflorian (Florian Pelz)
2024-10-06 7:09 ` pelzflorian (Florian Pelz)
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=87a5grihr2.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=72867@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
--cc=nigko.yerden@gmail.com \
--cc=pelzflorian@pelzflorian.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 external index
https://git.savannah.gnu.org/cgit/guix.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.