From: "Ludovic Courtès" <ludo@gnu.org>
To: Nicolas Graves <ngraves@ngraves.fr>
Cc: 65597-done@debbugs.gnu.org
Subject: bug#65597: [PATCH] gnu: ublock-origin: Update to 1.51.0.
Date: Thu, 28 Sep 2023 11:28:34 +0200 [thread overview]
Message-ID: <87pm22y7ct.fsf@gnu.org> (raw)
In-Reply-To: <9bdb1268e65a96c3744d1a83fe99532de6073df1.1693328341.git.ngraves@ngraves.fr> (Nicolas Graves's message of "Tue, 29 Aug 2023 18:59:01 +0200")
Hi,
Nicolas Graves <ngraves@ngraves.fr> skribis:
> * gnu/packages/browser-extensions.scm
> (ublock-main-assets): Add origin.
> (ublock-prod-assets): Add origin.
> (ublock-origin): Update to 1.51.0.
> [source]: Dropped (recursive? #t).
> [arguments]: Rewrite phase do-not-depend-on-git. Use gexp.
Finally applied, thanks!
Ludo’.
prev parent reply other threads:[~2023-09-28 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 16:59 [bug#65597] [PATCH] gnu: ublock-origin: Update to 1.51.0 Nicolas Graves via Guix-patches via
2023-09-28 9:28 ` Ludovic Courtès [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=87pm22y7ct.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=65597-done@debbugs.gnu.org \
--cc=ngraves@ngraves.fr \
/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).