From: camoz <camoz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: foot: update to 1.12.1.
Date: Tue, 10 May 2022 14:13:51 +0200 [thread overview]
Message-ID: <20220510121351.kzg_GeTIFqmElmdGWmRBJm6GhYSYK7pUechaFEy9jeY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36884@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
New comment by camoz on void-packages repository
https://github.com/void-linux/void-packages/pull/36884#issuecomment-1122310608
Comment:
I just want to highlight that this upgrade (with or without the `conf_files` option) has the potential to delete the user's configuration, because `/etc/xdg/foot/foot.ini` has already been the standard location for a system-wide foot config for some time. What is new in 1.12 is just that a default config is being installed there. So if void really wants to avoid overwriting the user's config, this should not be merged in the current state.
next prev parent reply other threads:[~2022-05-10 12:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 18:52 [PR PATCH] " ifreund
2022-04-27 19:47 ` camoz
2022-05-04 19:29 ` ftrvxmtrx
2022-05-04 20:35 ` camoz
2022-05-09 1:14 ` ericonr
2022-05-10 11:09 ` [PR PATCH] [Updated] " ifreund
2022-05-10 11:09 ` ifreund
2022-05-10 11:29 ` [PR PATCH] [Updated] " ifreund
2022-05-10 12:13 ` camoz [this message]
2022-05-10 12:16 ` ifreund
2022-05-16 9:04 ` [PR PATCH] [Updated] " ifreund
2022-05-16 9:10 ` ifreund
2022-05-16 9:23 ` ifreund
2022-05-16 9:55 ` r-ricci
2022-05-16 10:21 ` [PR PATCH] [Updated] " ifreund
2022-05-16 10:21 ` ifreund
2022-05-17 15:37 ` [PR PATCH] [Updated] " ifreund
2022-05-17 16:03 ` ifreund
2022-05-19 14:58 ` ifreund
2022-05-19 17:19 ` [PR PATCH] [Merged]: " ericonr
2022-05-16 6:50 [PR PATCH] " dkwo
2022-05-16 6:58 ` dkwo
2022-05-16 8:45 ` ifreund
2022-05-16 8:53 ` dkwo
2022-05-16 9:11 ` ifreund
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=20220510121351.kzg_GeTIFqmElmdGWmRBJm6GhYSYK7pUechaFEy9jeY@z \
--to=camoz@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).