From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 33928@debbugs.gnu.org
Subject: [bug#33928] [PATCH] gnu: hashcat: Update to 5.1.0.
Date: Wed, 09 Jan 2019 17:07:54 +0100 [thread overview]
Message-ID: <87ftu14xwl.fsf@gnu.org> (raw)
In-Reply-To: <ae5bf8841cbb9b611c4aad98ff099f8cec0aed60.1546196811.git.leo@famulari.name> (Leo Famulari's message of "Sun, 30 Dec 2018 14:06:51 -0500")
Hi!
Leo Famulari <leo@famulari.name> skribis:
> * gnu/packages/password-utils.scm (hashcat): Update to 5.1.0.
I haven’t tested but it looks harmless, please go ahead!
Ludo’.
prev parent reply other threads:[~2019-01-09 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 19:06 [bug#33928] [PATCH] gnu: hashcat: Update to 5.1.0 Leo Famulari
2019-01-09 16:07 ` 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=87ftu14xwl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33928@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.