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

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

bug#43768: closed ([PATCH] gnu: zrythm: Update to 1.0.0-alpha.3.0.1.)


From: GNU bug Tracking System
Subject: bug#43768: closed ([PATCH] gnu: zrythm: Update to 1.0.0-alpha.3.0.1.)
Date: Tue, 06 Oct 2020 09:39:02 +0000

Your message dated Tue, 06 Oct 2020 11:38:22 +0200
with message-id <874kn74ru9.fsf@gnu.org>
and subject line Re: [bug#43768] [PATCH] gnu: zrythm: Update to 
1.0.0-alpha.3.0.1.
has caused the debbugs.gnu.org bug report #43768,
regarding [PATCH] gnu: zrythm: Update to 1.0.0-alpha.3.0.1.
to be marked as done.

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


-- 
43768: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=43768
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH] gnu: zrythm: Update to 1.0.0-alpha.3.0.1. Date: Fri, 02 Oct 2020 18:29:50 +0100 User-agent: Evolution 3.34.2
Hi,

This patch updates Zrythm. I explicitly enabled rtmidi support (it was
implicitly enabled before), and also removed the xdg-open patch as it's
no longer necessary (the full path to xdg-open is now stored during
configuration).

Also, the versioning scheme changed to follow SemVer 2.0 (see
PACKAGING.md for details). I don't think there should be any problems
upgrading since the previous versions started with 0.

Thanks,
Alex

Attachment: 0001-gnu-zrythm-Update-to-1.0.0-alpha.3.0.1.patch
Description: Text Data

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message --- Subject: Re: [bug#43768] [PATCH] gnu: zrythm: Update to 1.0.0-alpha.3.0.1. Date: Tue, 06 Oct 2020 11:38:22 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
Hello,

> This patch updates Zrythm. I explicitly enabled rtmidi support (it was
> implicitly enabled before), and also removed the xdg-open patch as it's
> no longer necessary (the full path to xdg-open is now stored during
> configuration).

Nice, applied thanks!

Mathieu


--- End Message ---

reply via email to

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