From: Raghav Gururajan via Guix-patches via <guix-patches@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>, 46653@debbugs.gnu.org
Subject: [bug#46653] Make some changes to Profanity stuff (v2)
Date: Tue, 23 Feb 2021 12:32:49 -0500 [thread overview]
Message-ID: <3cf8c70f-176e-74cb-d01e-15cd0043844a@raghavgururajan.name> (raw)
In-Reply-To: <73f708d8213aaac67e357bba5efd29fc6f8e1fbe.camel@student.tugraz.at>
[-- Attachment #1.1: Type: text/plain, Size: 533 bytes --]
Hi Leo!
> There is just one failing test here. If there's really no way around
> it, disable that one, but try to investigate the link error first.
I already tried disabling that test. Two other tests that comes next to
it fail in same way.
> Since this issue is related, we should really get to the roots of it.
> Let's hope for a response.
Yeah.
> The ordering of these patches seems a little weird. Could you group
> them so that it's libmesode, then profanity, then libstrophe?
Sure.
Regards,
RG.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2021-02-23 17:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 3:08 [bug#46653] Make some changes to Profanity stuff Raghav Gururajan via Guix-patches via
[not found] ` <handler.46653.B.161379050225230.ack@debbugs.gnu.org>
2021-02-23 17:08 ` [bug#46653] Make some changes to Profanity stuff (v2) Raghav Gururajan via Guix-patches via
2021-02-23 17:28 ` Leo Prikler
2021-02-23 17:32 ` Raghav Gururajan via Guix-patches via [this message]
2021-02-23 17:39 ` Leo Prikler
2021-02-23 17:41 ` Raghav Gururajan via Guix-patches via
2021-02-23 17:48 ` [bug#46653] Make some changes to Profanity stuff (v3) Raghav Gururajan via Guix-patches via
2021-02-23 18:01 ` Leo Prikler
2021-02-23 20:01 ` [bug#46653] Make some changes to Profanity stuff (v4) Raghav Gururajan via Guix-patches via
2021-02-24 0:02 ` bug#46653: " 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=3cf8c70f-176e-74cb-d01e-15cd0043844a@raghavgururajan.name \
--to=guix-patches@gnu.org \
--cc=46653@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
--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).