all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Juanma Barranquero <lekktu@gmail.com>, 37556@debbugs.gnu.org
Subject: bug#37556: gpg "-unknown" version string
Date: Tue, 01 Oct 2019 14:09:36 +0200	[thread overview]
Message-ID: <87sgoc8y67.fsf@gnus.org> (raw)
In-Reply-To: <85ftkdkfjv.fsf@gmail.com> (Noam Postavsky's message of "Mon, 30 Sep 2019 10:46:28 -0400")

Noam Postavsky <npostavs@gmail.com> writes:

> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>>> I don't understand why making -unknown equivalent to a lesser version
>>> makes sense.  Shouldn't 2.2.17 and 2.2.17-unknown in fact be equal?
>>
>> Should they?  2.2.17-pre and 2.2.17-alpha should be less than 2.2.17,
>> but how do we know that -unknown isn't something -alpha-ish?
>
> It's "unknown", so it could be something opposite-of-alpha-ish too,
> right?  On average, 0 seems right.

That's possible.  Does anybody know how usual these -unknown things are,
and why they exist?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-10-01 12:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-29 22:59 bug#37556: gpg "-unknown" version string Juanma Barranquero
2019-09-30  5:34 ` Lars Ingebrigtsen
2019-09-30  7:17   ` Eli Zaretskii
2019-09-30  7:49     ` Juanma Barranquero
2019-09-30  8:46       ` Eli Zaretskii
2019-09-30  9:32         ` Juanma Barranquero
2019-09-30 14:04           ` Lars Ingebrigtsen
2019-09-30 14:25       ` Noam Postavsky
2019-09-30 14:42         ` Lars Ingebrigtsen
2019-09-30 14:46           ` Noam Postavsky
2019-10-01 12:09             ` Lars Ingebrigtsen [this message]
2019-10-01 14:59               ` Kazuhiro Ito
2019-10-13  3:01 ` Lars Ingebrigtsen
2019-10-13  5:12   ` Juanma Barranquero

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=87sgoc8y67.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=37556@debbugs.gnu.org \
    --cc=lekktu@gmail.com \
    --cc=npostavs@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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.