From: Paul Eggert <eggert@cs.ucla.edu>
To: Simon Josefsson <simon@josefsson.org>, bug-gnulib@gnu.org
Subject: Re: maint.mk: announce-gen with --no-print-checksums?
Date: Wed, 12 May 2021 14:25:49 -0700 [thread overview]
Message-ID: <ff66151b-39de-9d93-1efa-2e65fb9d9eda@cs.ucla.edu> (raw)
In-Reply-To: <871rabu2s6.fsf@latte.josefsson.org>
On 5/12/21 1:15 PM, Simon Josefsson via Gnulib discussion list wrote:
> I'm somewhat
> inclined to follow their path and add support for base64 encoded hashes
> in 'sha256sum', and then use that in announcen-gen.
Sounds good to me. I suppose it would be a --base64 option?
At some point we might want to make --base64 the default....
prev parent reply other threads:[~2021-05-12 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 20:15 maint.mk: announce-gen with --no-print-checksums? Simon Josefsson via Gnulib discussion list
2021-05-12 21:25 ` Paul Eggert [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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff66151b-39de-9d93-1efa-2e65fb9d9eda@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bug-gnulib@gnu.org \
--cc=simon@josefsson.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.
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).