From: Martin Becze <mjbecze@riseup.net>
To: 44969@debbugs.gnu.org
Cc: Martin Becze <mjbecze@riseup.net>
Subject: [bug#44969] [PATCH 0/7] Update trezord to 2.0.30
Date: Mon, 30 Nov 2020 14:17:57 -0600 [thread overview]
Message-ID: <20201130201757.27248-1-mjbecze@riseup.net> (raw)
This updates trezod to 2.0.30
Martin Becze (7):
gnu: go-github-com-gorilla-mux: Update to 1.8.0.
gnu: Added go-github-com-felixge-httpsnoop.
gnu: Added go-github-com-gorilla-handlers.
gnu: Added go-github-com-gorilla-securecookie.
gnu: Added go-github-com-gorilla-csrf.
gnu: Added go-gopkg-in-natefinch-lumberjack.v2.
gnu: trezord: Updated to 2.0.30.
gnu/packages/finance.scm | 14 ++-
gnu/packages/golang.scm | 186 ++++++++++++++++++++++++++++++++-------
2 files changed, 165 insertions(+), 35 deletions(-)
--
2.29.2
next reply other threads:[~2020-11-30 20:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 20:17 Martin Becze [this message]
2020-11-30 20:24 ` [bug#44969] [PATCH 1/7] gnu: go-github-com-gorilla-mux: Update to 1.8.0 Martin Becze
2020-11-30 20:24 ` [bug#44969] [PATCH 2/7] gnu: Added go-github-com-felixge-httpsnoop Martin Becze
2020-12-08 9:01 ` Christopher Baines
2020-11-30 20:24 ` [bug#44969] [PATCH 3/7] gnu: Added go-github-com-gorilla-handlers Martin Becze
2020-11-30 20:24 ` [bug#44969] [PATCH 4/7] gnu: Added go-github-com-gorilla-securecookie Martin Becze
2020-11-30 20:24 ` [bug#44969] [PATCH 5/7] gnu: Added go-github-com-gorilla-csrf Martin Becze
2020-11-30 20:24 ` [bug#44969] [PATCH 6/7] gnu: Added go-gopkg-in-natefinch-lumberjack.v2 Martin Becze
2020-11-30 20:24 ` [bug#44969] [PATCH 7/7] gnu: trezord: Updated to 2.0.30 Martin Becze
2020-12-08 8:59 ` [bug#44969] [PATCH 1/7] gnu: go-github-com-gorilla-mux: Update to 1.8.0 Christopher Baines
2020-12-08 8:55 ` bug#44969: [PATCH 0/7] Update trezord to 2.0.30 Christopher Baines
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=20201130201757.27248-1-mjbecze@riseup.net \
--to=mjbecze@riseup.net \
--cc=44969@debbugs.gnu.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).