From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: socat test 2.0.0-b9-1
Date: Tue, 31 Mar 2020 07:32:25 +0200 [thread overview]
Message-ID: <a6434743-ff67-5260-a65d-e6c402af799e@gmail.com> (raw)
Dear Andrew
I think the Version-Release of your test package is confusing,
as we have two dashes instead of only one.
It will also make a hypothetical future upgrade hard.
Is 2.0.0-1 major of 2.0.0-b9-1 ?
Regards
Marco
PS: I wonder if having a test version 4 years old that is clearly not
moving at all and not bug fixed really worth to have
http://www.dest-unreach.org/socat/
next reply other threads:[~2020-03-31 5:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 5:32 Marco Atzeri [this message]
2020-03-31 16:19 ` ASSI
2020-03-31 17:41 ` Marco Atzeri
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=a6434743-ff67-5260-a65d-e6c402af799e@gmail.com \
--to=marco.atzeri@gmail.com \
--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).