From: "Ludovic Courtès" <ludo@gnu.org>
To: Massimo Zaniboni <mzan@dokmelody.org>
Cc: 74513-done@debbugs.gnu.org
Subject: bug#74513: [PATCH] gnu: goaccess: Update to 1.9.3.
Date: Thu, 26 Dec 2024 23:15:40 +0100 [thread overview]
Message-ID: <87zfkixf8z.fsf@gnu.org> (raw)
In-Reply-To: <d8f8239a1c0650343a8c75cabc5a4ea5e611e77d.1732480232.git.mzan@dokmelody.org> (Massimo Zaniboni's message of "Sun, 24 Nov 2024 21:30:32 +0100")
Massimo Zaniboni <mzan@dokmelody.org> skribis:
> gnu: goaccess: Update to 1.9.3.
>
> * gnu/packages/web.scm (goaccess): Update to 1.9.3.
>
> Change-Id: Ie3cc2de51678e06cf602b3cdb5883751e4763d8e
Applied, thanks!
prev parent reply other threads:[~2024-12-26 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-24 20:30 [bug#74513] [PATCH] gnu: goaccess: Update to 1.9.3 Massimo Zaniboni
2024-12-26 22:15 ` 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=87zfkixf8z.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=74513-done@debbugs.gnu.org \
--cc=mzan@dokmelody.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).