emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#69272: closed ([PATCH 0/4] Refactor prosody modules, and add prosody


From: GNU bug Tracking System
Subject: bug#69272: closed ([PATCH 0/4] Refactor prosody modules, and add prosody-vcard-muc.)
Date: Sat, 02 Mar 2024 13:02:02 +0000

Your message dated Sat, 02 Mar 2024 14:00:15 +0100
with message-id <c90b839bacd2035585e61a22f807e01b84d75404.camel@gmail.com>
and subject line Re: [bug#69272] [PATCH v2 4/4] gnu: Add prosody-vcard-muc.
has caused the debbugs.gnu.org bug report #69272,
regarding [PATCH 0/4] Refactor prosody modules, and add prosody-vcard-muc.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
69272: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=69272
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH 0/4] Refactor prosody modules, and add prosody-vcard-muc. Date: Mon, 19 Feb 2024 23:31:03 +1100
I wanted to add prosody-vcard-muc, which is a prosody module. When I saw the
code for the two existing modules I thought it could use a refactor before
adding it, so I did that, too.

I have successfully reconfigured my prosody server, which uses all three of
the Guix-packaged prosody modules, with this change.

Carlo Zancanaro (4):
  gnu: Extract prosody-module from existing prosody modules.
  gnu: Use copy-build-system for prosody modules.
  gnu: Update prosody modules to the newest revision.
  gnu: Add prosody-vcard-muc.

 gnu/packages/messaging.scm | 88 +++++++++++++++++---------------------
 1 file changed, 39 insertions(+), 49 deletions(-)


base-commit: 07ecdb99b6c4b6b3e993d08034138bf69414020b
-- 
2.41.0




--- End Message ---
--- Begin Message --- Subject: Re: [bug#69272] [PATCH v2 4/4] gnu: Add prosody-vcard-muc. Date: Sat, 02 Mar 2024 14:00:15 +0100 User-agent: Evolution 3.46.4
Am Samstag, dem 02.03.2024 um 22:27 +1100 schrieb Carlo Zancanaro:
> P.S. Apologies that you'll get this message twice. I forgot to Cc the
> bug tracer on the first attempt.
Apologies from me for not checking earlier.

Pushed now, thanks!



--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]