From: Felix Lechner via Guix-patches via <guix-patches@gnu.org>
To: 58658@debbugs.gnu.org
Cc: mail@cbaines.net
Subject: [bug#58658] [PATCH staging] gnu: go-golang-org-x-net: Update to 0.5.0.
Date: Thu, 5 Jan 2023 06:40:43 -0800 [thread overview]
Message-ID: <20230105144046.2994-1-felix.lechner@lease-up.com> (raw)
In-Reply-To: <CAFHYt54A9Bh5-cYz8ywhsdk2h0NMxC-=CnEMmwjLh7vbU_e0hA@mail.gmail.com>
Hi,
This updates the Golang modules to their latest available versions,
and rebases the patch series onto staging.
Kind regards
Felix Lechner
next prev parent reply other threads:[~2023-01-05 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 12:47 [bug#58658] [PATCH] go-golang-org-x-net: Update to 0.1.0 Felix Lechner via Guix-patches via
2022-11-20 11:22 ` Christopher Baines
2022-11-20 13:20 ` Felix Lechner via Guix-patches via
2022-12-19 19:40 ` [bug#58658] [PATCH v2] gnu: " Felix Lechner via Guix-patches via
2022-12-19 19:40 ` [bug#58658] [PATCH v2 1/3] gnu: go-golang-org-x-sys: Update to 0.3.0 Felix Lechner via Guix-patches via
2022-12-19 19:40 ` [bug#58658] [PATCH v2 2/3] gnu: go-golang-org-x-net: Update to 0.1.0 Felix Lechner via Guix-patches via
2022-12-19 19:40 ` [bug#58658] [PATCH v2 3/3] gnu: go-golang-zx2c4-com-wireguard: Update to 0.0.20211016 Felix Lechner via Guix-patches via
2022-12-21 22:41 ` [bug#58658] Now needs to go into staging Felix Lechner via Guix-patches via
2023-01-05 14:40 ` Felix Lechner via Guix-patches via [this message]
2023-01-05 14:40 ` [bug#58658] [PATCH v3 1/3] gnu: go-golang-org-x-sys: Update to 0.4.0 Felix Lechner via Guix-patches via
2023-01-05 14:40 ` [bug#58658] [PATCH v3 2/3] gnu: go-golang-org-x-net: Update to 0.5.0 Felix Lechner via Guix-patches via
2023-01-05 14:40 ` [bug#58658] [PATCH v3 3/3] gnu: go-golang-zx2c4-com-wireguard: Update to 0.0.20211016 Felix Lechner via Guix-patches via
2023-03-05 21:01 ` bug#58658: Superseded by new bug Felix Lechner via Guix-patches via
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=20230105144046.2994-1-felix.lechner@lease-up.com \
--to=guix-patches@gnu.org \
--cc=58658@debbugs.gnu.org \
--cc=felix.lechner@lease-up.com \
--cc=mail@cbaines.net \
/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).