From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: NetworkManager: Set elogind on by default.
Date: Sun, 08 Sep 2019 17:09:42 +0200 [thread overview]
Message-ID: <20190908150942.BCccW0ns6_mgaQ1jEYcdUWDjP2MX0_LRl985WC3fb9U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14277@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
New comment by thomas-t-w on void-packages repository
https://github.com/void-linux/void-packages/pull/14277#issuecomment-529211754
Comment:
I think that eventually we could. I was originally going to do that but I am usually pretty conservative when it comes to things like this though. I guess it comes from me needing accessibility software and people making changes to programs that break that all the time. I think that maybe its good to leave it around for a while to make it easier to revert if someone has some obscure issue. Void serves many use cases and I don't want to break someones workflow. My vote would be to leave it around for a while (two weeks or so) and see if someone complains. What do you think about this?
next prev parent reply other threads:[~2019-09-08 15:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 23:53 [PR PATCH] t voidlinux-github
2019-09-06 23:55 ` t voidlinux-github
2019-09-08 0:44 ` NetworkManager: Set elogind on by default voidlinux-github
2019-09-08 0:59 ` voidlinux-github
2019-09-08 2:13 ` voidlinux-github
2019-09-08 2:34 ` voidlinux-github
2019-09-08 13:24 ` voidlinux-github
2019-09-08 15:09 ` voidlinux-github [this message]
2019-09-09 12:15 ` voidlinux-github
2019-09-09 12:46 ` voidlinux-github
2019-09-09 13:44 ` voidlinux-github
2019-09-09 14:07 ` voidlinux-github
2019-09-09 14:12 ` voidlinux-github
2019-09-09 14:47 ` voidlinux-github
2019-09-11 11:42 ` [PR PATCH] [Merged]: " voidlinux-github
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=20190908150942.BCccW0ns6_mgaQ1jEYcdUWDjP2MX0_LRl985WC3fb9U@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).