Received: from listserv.local (listserv [172.16.8.22])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTP id C8329780FE5;
	Sun, 19 Jun 2022 13:27:52 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
To: Drew DeVault <sir@cmpwn.com>
From: omni <no-reply@dispatch.alpinelinux.org>
Cc: ~alpine/aports@lists.alpinelinux.org
In-Reply-To: <20220619123915.7372-1-sir@cmpwn.com>
Subject: Re: [PATCH] testing/himitsu-ssh: upgrade to
 1984a42ebfc0a4975c05aa8fc1d4030010b0c8db
Date: Sun, 19 Jun 2022 13:27:52 -0000
Message-ID: 
 <165564527277.985.12198358908305277493.gitlab.35483.361908cee072696e0ea073489c9b1af7c2bd3867@listserv.local>

Aha, I haven't seen that. Usually `0_git20220619`, from `CommitDate`, is the `pkgver` after all and would imply the latest commit on that date, but I'm not sure how you'd then handle fast iterations, where you want to update a package the same day it's already been upgraded to an earlier commit of the current day. I guess that'd be a corner case.

-- 
via https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/35483#note_242635