|
From: | GNU bug Tracking System |
Subject: | bug#38267: closed (upgrade brlaser) |
Date: | Tue, 19 Nov 2019 21:06:02 +0000 |
Your message dated Tue, 19 Nov 2019 22:05:09 +0100 with message-id <address@hidden> and subject line Re: [bug#38267] upgrade brlaser has caused the debbugs.gnu.org bug report #38267, regarding upgrade brlaser to be marked as done. (If you believe you have received this mail in error, please contact address@hidden.) -- 38267: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=38267 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: upgrade brlaser Date: Tue, 19 Nov 2019 11:06:07 +0100 Hi, yesterday I notified brlaser maintainer that a package is available on guix and he asked us to upgrade (https://github.com/pdewacht/brlaser/pull/55), so here's the patch.I moved from using the commit # to the released version.Since the let block was not needed anymore, the patch is unnecessary ugly, let me know if I need to format it differentlyThanks, Nicolò0001-gnu-packages-printers.scm-brlaser-Update-to-v6.patch
Description: Text Data
--- End Message ---
--- Begin Message ---Subject: Re: [bug#38267] upgrade brlaser Date: Tue, 19 Nov 2019 22:05:09 +0100 User-agent: Notmuch/0.29.1 (https://notmuchmail.org) Emacs/26.3 (x86_64-pc-linux-gnu) Nicolò Balzarotti <address@hidden> writes: > Hi, yesterday I notified brlaser maintainer that a package is available on > guix and he asked us to upgrade (https://github.com/pdewacht/brlaser/pull/55), > so here's the patch. Nice, applied (with a conventional commit message), thank you! I will happily accept a follow-up patch that removes all the printer product names with something like "known to work with a wide array of Brother printers, consult @url{foo,https://bar} for the full list". WDYT? :-)signature.asc
Description: PGP signature
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |