all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 57052@debbugs.gnu.org, maxim.cournoyer@gmail.com,
	liliana.prikler@ist.tugraz.at
Cc: cairn@pm.me
Subject: bug#57052: elogind-service specifies a variable that's ignored by defualt
Date: Tue, 09 Aug 2022 14:31:49 +0000	[thread overview]
Message-ID: <6AE7F282-3FD0-415F-A460-9AB1A5539A13@tobias.gr> (raw)
In-Reply-To: <87wnbho6z2.fsf@gmail.com>

>For the record, this was noticed and discussed more than a year ago, see
>Message-ID: <871rens9a2.fsf@nckx>.  It had fallen into the cracks

LOL.  I'm the one who asked Cairn to report this.  I didn't remember publicly reporting it, I only remembered noticing it and not fixing it, and didn't want it to get forgotten 'again'.  Sorry for the noise!

Strongly disagree that the current Guix behaviour makes any sense, let alone better!  That sounds like posthockholm rationalisation to me.  If people want opinionated variants, those can be written on top of a service that properly exposes upstream behaviour.


Kind regards,

T G-R

Sent on the go.  Excuse or enjoy my brevity.




  reply	other threads:[~2022-08-09 14:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-07 23:29 bug#57052: elogind-service specifies a variable that's ignored by defualt Cairn via Bug reports for GNU Guix
2022-08-08 10:45 ` Liliana Marie Prikler
2022-08-09  1:52   ` bokr
2022-08-09  6:34     ` Liliana Marie Prikler
2022-08-09  6:42   ` Cairn via Bug reports for GNU Guix
2022-08-09 13:52   ` Maxim Cournoyer
2022-08-09 13:57     ` Maxim Cournoyer
2022-08-09 14:31       ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2022-08-09 14:42         ` Cairn via Bug reports for GNU Guix
2022-08-10  4:38           ` Maxim Cournoyer

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=6AE7F282-3FD0-415F-A460-9AB1A5539A13@tobias.gr \
    --to=bug-guix@gnu.org \
    --cc=57052@debbugs.gnu.org \
    --cc=cairn@pm.me \
    --cc=liliana.prikler@ist.tugraz.at \
    --cc=maxim.cournoyer@gmail.com \
    --cc=me@tobias.gr \
    /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.