From: "Ludovic Courtès" <ludo@gnu.org>
To: Carl Dong <contact@carldong.me>
Cc: 39219@debbugs.gnu.org, M F <fanquake@gmail.com>
Subject: [bug#39219] [PATCH] gnu: bitcoin-core: Update to 0.19.0.1.
Date: Fri, 24 Jan 2020 23:58:32 +0100 [thread overview]
Message-ID: <87ftg4cvhj.fsf@gnu.org> (raw)
In-Reply-To: <FA4CF0BA-5455-4A5D-B884-A8520E08161F@carldong.me> (Carl Dong's message of "Tue, 21 Jan 2020 16:02:13 +0000")
Hello,
Carl Dong <contact@carldong.me> skribis:
> * gnu/packages/finance.scm (bitcoin-core): Update to 0.19.0.1.
>
> Co-authored-by: fanquake <fanquake@gmail.com>
Go for it!
Thanks,
Ludo’.
prev parent reply other threads:[~2020-01-24 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 16:02 [bug#39219] [PATCH] gnu: bitcoin-core: Update to 0.19.0.1 Carl Dong
2020-01-24 22:58 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftg4cvhj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=39219@debbugs.gnu.org \
--cc=contact@carldong.me \
--cc=fanquake@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.