From: Eric Biggers <ebiggers@kernel.org>
To: Colin Walters <walters@verbum.org>
Cc: linux-fscrypt@vger.kernel.org
Subject: Re: version/tags for fsverity-utils
Date: Wed, 6 Nov 2019 10:43:32 -0800 [thread overview]
Message-ID: <20191106184332.GC2766@sol.localdomain> (raw)
In-Reply-To: <3c1e9aca-2390-4350-a19d-baff6a065c6a@www.fastmail.com>
On Wed, Nov 06, 2019 at 10:57:08AM -0500, Colin Walters wrote:
> Hi, I'm looking at fsverity for Fedora CoreOS (a bit more background in https://github.com/ostreedev/ostree/pull/1959 )
> I have a bunch of questions there (feel free to jump in), but just to start here:
>
> I'd like to get fsverity-utils as a Fedora package, but there don't seem to be any git tags on the repo https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/fsverity-utils.git/ - I could make up a datestamped version number, but I think it'd be better if there were upstream tags - it is useful to have releases with human-consumable version numbers for the usual reasons. And RPM/dpkg/etc really care about the version numbers of packages.
>
> Other distributions/some packagers think "release" means tarballs, so someone may want to consider that too, personally
> I use https://github.com/cgwalters/git-evtag for making git tags since I think it helps replace tarballs.
Yes, I think it's time for a formal release of fsverity-utils now that fs-verity
is in the upstream kernel. I've tagged v1.0 and uploaded the tarball to here:
https://kernel.org/pub/linux/kernel/people/ebiggers/fsverity-utils/v1.0/
- Eric
prev parent reply other threads:[~2019-11-06 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 15:57 version/tags for fsverity-utils Colin Walters
2019-11-06 18:43 ` Eric Biggers [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191106184332.GC2766@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=walters@verbum.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 NNTP newsgroup(s).