From: Tanguy Le Carrour <tanguy@bioneland.org>
To: 37923@debbugs.gnu.org
Subject: [bug#37923] [PATCH 0/2] gnu: profanity: Add configure flags and inputs for better defaults.
Date: Fri, 25 Oct 2019 17:17:11 +0200 [thread overview]
Message-ID: <20191025151711.aoqcwzuz7vwcgdbm@rafflesia> (raw)
This makes OMEMO and desktop notifications available.
As Jack mentioned [1], the home page was redirected. I've updated it.
[1]: https://lists.gnu.org/archive/html/guix-devel/2019-10/msg00610.html
--
Tanguy
next reply other threads:[~2019-10-25 15:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 15:17 Tanguy Le Carrour [this message]
2019-10-25 15:20 ` [bug#37923] [PATCH 1/2] gnu: profanity: Add configure flags and inputs for better defaults Tanguy Le Carrour
2019-10-25 15:20 ` [bug#37923] [PATCH 2/2] gnu: profanity: Update home-page URL Tanguy Le Carrour
2019-10-25 17:25 ` [bug#37923] [PATCH 1/2] gnu: profanity: Add configure flags and inputs for better defaults Mathieu Othacehe
2019-10-26 16:12 ` Tanguy Le Carrour
2019-10-26 16:16 ` [bug#37923] [PATCH v2 1/4] " tanguy
2019-10-26 16:16 ` [bug#37923] [PATCH v2 2/4] gnu: profanity: Update home-page URL tanguy
2019-10-26 16:16 ` [bug#37923] [PATCH v2 3/4] gnu: profanity: Add configure flags, so that build fail if libs are missing tanguy
2019-10-26 16:16 ` [bug#37923] [PATCH v2 4/4] gnu: profanity: Add configure flags for better defaults tanguy
2019-10-26 21:09 ` [bug#37923] [PATCH 0/4] gnu: profanity: Add configure flags and inputs " Tanguy Le Carrour
2019-10-26 21:11 ` [bug#37923] [PATCH v3 1/4] " tanguy
2019-10-26 21:11 ` [bug#37923] [PATCH v3 2/4] gnu: profanity: Update home-page URL tanguy
2019-10-26 21:11 ` [bug#37923] [PATCH v3 3/4] gnu: profanity: Add configure flags, so that build fail if libs are missing tanguy
2019-10-26 21:11 ` [bug#37923] [PATCH v3 4/4] gnu: profanity: Add configure flags for better defaults tanguy
2019-10-28 10:31 ` [bug#37923] [PATCH v3 1/4] gnu: profanity: Add configure flags and inputs " Mathieu Othacehe
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=20191025151711.aoqcwzuz7vwcgdbm@rafflesia \
--to=tanguy@bioneland.org \
--cc=37923@debbugs.gnu.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.