From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Raghav Gururajan <rg@raghavgururajan.name>, 45954@debbugs.gnu.org
Subject: [bug#45954] Telegram-CLI (v9)
Date: Wed, 03 Feb 2021 09:16:47 +0100 [thread overview]
Message-ID: <4467685fc58b1f3da3305711bc19345819a06d6c.camel@student.tugraz.at> (raw)
In-Reply-To: <1828c834-eb18-5ee6-deeb-c3b55bbe248a@raghavgururajan.name>
Hello Raghav,
Am Dienstag, den 02.02.2021, 20:56 -0500 schrieb Raghav Gururajan:
> + (,@%gnu-build-system-modules
> + (guix build copy-build-system))
> + #:modules
> + ((guix build gnu-build-system)
> + ((guix build copy-build-system)
> + #:prefix copy:)
> + (guix build utils))
It is Guix convention to put the added component in front of the
others, i.e.
> + ((guix build copy-build-system)
> + ,@%gnu-build-system-modules)
and so on. Otherwise LGTM so far; I'll be doing functionality tests
later today. If you don't send v10 by then, I can also make that
change for you.
Regards,
Leo
next prev parent reply other threads:[~2021-02-03 8:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 9:16 [bug#45954] Telegram-CLI Raghav Gururajan
2021-01-19 15:08 ` [bug#45954] Telegram-CLI (v2) Raghav Gururajan
2021-01-20 10:44 ` [bug#45954] Telegram-CLI (v3) Raghav Gururajan
2021-01-22 4:44 ` [bug#45954] Telegram-CLI (v4) Raghav Gururajan
2021-01-28 1:00 ` [bug#45954] Telegram-CLI (v5) Raghav Gururajan
2021-01-31 19:46 ` [bug#45954] Telegram-CLI (v6) Raghav Gururajan
2021-02-01 8:30 ` Leo Prikler
2021-02-01 22:18 ` Raghav Gururajan
2021-02-01 22:08 ` [bug#45954] Telegram-CLI (v7) Raghav Gururajan
2021-02-01 22:39 ` Leo Prikler
2021-02-02 2:33 ` Raghav Gururajan
2021-02-02 9:50 ` [bug#45954] Telegram-CLI (v7/v8) Leo Prikler
2021-02-03 2:41 ` Raghav Gururajan
2021-02-02 2:25 ` [bug#45954] Telegram-CLI (v8) Raghav Gururajan
2021-02-03 1:56 ` [bug#45954] Telegram-CLI (v9) Raghav Gururajan
2021-02-03 8:16 ` Leo Prikler [this message]
2021-02-03 17:52 ` Raghav Gururajan
2021-02-03 17:50 ` [bug#45954] Telegram-CLI (v10) Raghav Gururajan
2021-02-03 18:18 ` bug#45954: " Leo Prikler
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4467685fc58b1f3da3305711bc19345819a06d6c.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=45954@debbugs.gnu.org \
--cc=rg@raghavgururajan.name \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).