From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: New version of GNU ddrescue available (1.26)
Date: Wed, 6 Jul 2022 13:28:25 -0600 [thread overview]
Message-ID: <0d00cd5f-5a47-af88-1333-82538d931c8a@SystematicSw.ab.ca> (raw)
In-Reply-To: <2424f029-a202-68b1-721f-72d995787208@hamishmb.com>
On 2022-07-06 09:13, Hamish McIntyre-Bhatty wrote:
> On 05/07/2022 10:22, Christian Franke wrote:
>> Hamish McIntyre-Bhatty wrote:
>>> I was wondering if the maintainer for GNU ddrescue could update to
>>> 1.26 please?
>>
>> 1.27-pre2 is already released, so I wait for 1.27 final.
>>
>
> Fair enough. Do you know if there's a mailing list or similar to be
> notified of new versions? I was on the GNU mailing list for a bit, but I
> couldn't configure it to not just constantly spam me.
I like RSS feeds via browser extensions (e.g. Foxish live RSS) from:
https://www.mail-archive.com/bug-ddrescue@gnu.org/maillist.xml
https://www.mail-archive.com/info-gnu@gnu.org/maillist.xml
but you can monitor or subscribe to the GNU mailing lists directly.
You could also monitor updates to:
https://download.savannah.gnu.org/releases/ddrescue/
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2022-07-06 19:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 9:04 Hamish McIntyre-Bhatty
2022-07-05 9:22 ` Christian Franke
2022-07-06 15:13 ` Hamish McIntyre-Bhatty
2022-07-06 15:43 ` Christian Franke
2022-07-06 19:28 ` Brian Inglis [this message]
2022-07-07 11:51 ` Hamish McIntyre-Bhatty
2022-07-08 6:07 ` Brian Inglis
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=0d00cd5f-5a47-af88-1333-82538d931c8a@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-apps@cygwin.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.
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).