From: Andrew Tropin <andrew@trop.in>
To: 58484@debbugs.gnu.org
Cc: "\(" <paren@disroot.org>
Subject: [bug#58484] [PATCH 1/1] gnu: home: home-dbus-service-type: Fix make-forkexec-constructor call.
Date: Fri, 14 Oct 2022 11:11:58 +0400 [thread overview]
Message-ID: <87v8omlw01.fsf@trop.in> (raw)
In-Reply-To: <20221013064825.6731-1-paren@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
On 2022-10-13 07:48, guix-patches@gnu.org wrote:
> * gnu/home/services/desktop.scm (home-dbus-shepherd-services)[start]
> <#:environment-variables>: Use a quote instead of a gexp.
> ---
It's possible to type arbitrary text after ---, which won't be added to
commit message or affect a patch. Just in case you would like to send
one email instead of two, this trick can be used.
> gnu/home/services/desktop.scm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gnu/home/services/desktop.scm b/gnu/home/services/desktop.scm
> index 6549efd8df..e94e666d93 100644
> --- a/gnu/home/services/desktop.scm
> +++ b/gnu/home/services/desktop.scm
> @@ -201,7 +201,7 @@ (define (home-dbus-shepherd-services config)
> (format #f "/run/user/~a"
> (getuid)))))
> #:environment-variables
> - #~(list "DBUS_VERBOSE=1")
> + '(list "DBUS_VERBOSE=1")
> #:log-file
> (format #f "~a/dbus.log"
> (or (getenv "XDG_LOG_HOME")
Applied, pushed, thank you :)
--
Best regards,
Andrew Tropin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-10-14 7:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 6:47 [bug#58484] [PATCH 0/1] gnu: home: home-dbus-service-type: Fix make-forkexec-constructor call ( via Guix-patches via
2022-10-13 6:48 ` [bug#58484] [PATCH 1/1] " ( via Guix-patches via
2022-10-14 7:11 ` Andrew Tropin [this message]
2022-10-14 7:12 ` ( via Guix-patches via
2022-10-14 7:18 ` ( via Guix-patches via
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=87v8omlw01.fsf@trop.in \
--to=andrew@trop.in \
--cc=58484@debbugs.gnu.org \
--cc=paren@disroot.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/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.