From: Marius Bakke <mbakke@fastmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>,
Efraim Flashner <efraim@flashner.co.il>
Cc: 36000@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
"Nicolas Goaziou" <mail@nicolasgoaziou.fr>
Subject: [bug#36000] Acknowledgement ([PATCH 1/4] guix: Add helper for generating desktop entry files.)
Date: Fri, 18 Oct 2019 17:24:46 +0200 [thread overview]
Message-ID: <87d0euyt35.fsf@devup.no> (raw)
In-Reply-To: <87y2xihyea.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 230 bytes --]
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> Sorry, my email this morning meant "core-updates", as per the other
> comments in this thread!
>
> So should I merge on core-updates then?
If you think it is ready, go for it! :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-10-18 15:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 7:11 [bug#36000] [PATCH 1/4] guix: Add helper for generating desktop entry files Pierre Neidhardt
2019-05-30 8:17 ` [bug#36000] [PATCH 2/4] gnu: emacs-exwm: Use make-desktop-entry-file Pierre Neidhardt
2019-05-30 8:17 ` [bug#36000] [PATCH 3/4] gnu: tome4: " Pierre Neidhardt
2019-05-30 8:17 ` [bug#36000] [PATCH 4/4] gnu: drascula: " Pierre Neidhardt
[not found] ` <handler.36000.B.155920231822519.ack@debbugs.gnu.org>
2019-10-12 8:43 ` [bug#36000] Acknowledgement ([PATCH 1/4] guix: Add helper for generating desktop entry files.) Pierre Neidhardt
2019-10-12 18:44 ` Efraim Flashner
2019-10-12 19:05 ` Pierre Neidhardt
2019-10-12 19:12 ` Efraim Flashner
2019-10-18 8:43 ` Pierre Neidhardt
2019-10-18 14:40 ` Ludovic Courtès
2019-10-18 15:10 ` Marius Bakke
2019-10-18 15:13 ` Marius Bakke
2019-10-18 15:22 ` Pierre Neidhardt
2019-10-18 15:24 ` Marius Bakke [this message]
2019-10-19 10:46 ` Pierre Neidhardt
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=87d0euyt35.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=36000@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=ludo@gnu.org \
--cc=mail@ambrevar.xyz \
--cc=mail@nicolasgoaziou.fr \
/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.