From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>, 40485@debbugs.gnu.org
Subject: [bug#40485] Acknowledgement (gnu: Update libxfce4ui to 4.15.2.)
Date: Tue, 14 Apr 2020 19:07:33 +0200 [thread overview]
Message-ID: <87d08am1wq.fsf@nckx> (raw)
In-Reply-To: <39267250-afcc-1e79-db07-cd47756d0967@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 266 bytes --]
Naga, Danny,
What's the reason for adding an unstable version? We don't
usually do that in Guix.
Is this required for some other package?
Sorry for not bringing this up sooner; I'm still slogging through
the backlog in a most random way.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-04-14 17:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 12:55 [bug#40485] gnu: Update libxfce4ui to 4.15.2 Naga Malleswari
[not found] ` <handler.40485.B.158626413323635.ack@debbugs.gnu.org>
2020-04-07 13:40 ` [bug#40485] Acknowledgement (gnu: Update libxfce4ui to 4.15.2.) Naga Malleswari
2020-04-07 13:57 ` Danny Milosavljevic
2020-04-07 14:01 ` Danny Milosavljevic
2020-04-07 14:07 ` Danny Milosavljevic
2020-04-07 14:17 ` Naga Malleswari
2020-04-07 14:23 ` Danny Milosavljevic
2020-04-07 19:17 ` Naga Malleswari
2020-04-07 19:24 ` Danny Milosavljevic
2020-04-07 19:48 ` Danny Milosavljevic
2020-04-08 19:43 ` Naga Malleswari
2020-04-08 22:19 ` Danny Milosavljevic
2020-04-08 22:31 ` Danny Milosavljevic
2020-04-08 22:44 ` Danny Milosavljevic
2020-04-09 20:42 ` Naga Malleswari
2020-04-09 22:11 ` Danny Milosavljevic
2020-04-12 21:09 ` Naga Malleswari
2020-04-13 19:27 ` Danny Milosavljevic
2020-04-14 15:43 ` [bug#40485] [PATCH v3] : " Naga Malleswari
2020-04-14 17:07 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-04-19 15:59 ` bug#40485: " Danny Milosavljevic
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=87d08am1wq.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=40485@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--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.