From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 67944@debbugs.gnu.org
Cc: 67944-done@debbugs.gnu.org, csantosb@inventati.org
Subject: bug#67944: Broken package: emacs-mu4e-conversation
Date: Sat, 30 Dec 2023 23:45:23 -0500 [thread overview]
Message-ID: <87h6jzq8t8.fsf@gmail.com> (raw)
In-Reply-To: <87cyv0pj8t.fsf@inventati.org> (Cayetano Santos via Bug reports for's message of "Thu, 21 Dec 2023 00:01:32 +0100")
Hi,
Cayetano Santos via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
> Hi guix,
>
> As for the project readme, "Warning: As of 2021-01-06 this package is
> broken since mu4e has made changes to its protocol."
>
> We should probably remove it from guix.
Done!
--
Thanks,
Maxim
prev parent reply other threads:[~2023-12-31 4:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 23:01 bug#67944: Broken package: emacs-mu4e-conversation Cayetano Santos via Bug reports for GNU Guix
2023-12-31 4:45 ` Maxim Cournoyer [this message]
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=87h6jzq8t8.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=67944-done@debbugs.gnu.org \
--cc=67944@debbugs.gnu.org \
--cc=csantosb@inventati.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 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).