From: Mimi Zohar <zohar@kernel.org>
To: Vitaly Chikunov <vt@altlinux.org>, linux-integrity@vger.kernel.org
Cc: "Bruno E. O. Meneguele" <bmeneg@redhat.com>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
Petr Vorel <pvorel@suse.cz>
Subject: Re: ima-evm-utils: git tagging for release
Date: Tue, 30 Jul 2019 10:36:14 -0400 [thread overview]
Message-ID: <1564497374.4189.84.camel@kernel.org> (raw)
In-Reply-To: <1564486237.4189.28.camel@kernel.org>
On Tue, 2019-07-30 at 07:30 -0400, Mimi Zohar wrote:
> Hi Vitaly,
>
> On Tue, 2019-07-30 at 09:26 +0300, Vitaly Chikunov wrote:
> > Mimi,
> >
> > It seems that you are released v1.2 of ima-evm-utils. (I did not receive
> > any announcement on linux-integrity.) I noticed that you are not using
> > annotated tags for release versions.
>
> In the future, I'll announce it here.
>
> >
> > I suggest you use annotated tags (possible even signed) for release
> > versions. (You will need to delete existing v1.2 local tag if you are
> > going to retag it with annotated tag.)
Done
> There are a couple of additional bug fixes that need to be applied
> against the v1.2 release. Maybe it would be better to release v1.2.1
> with these additional bug fixes, using the annotated tag.
I've also pushed out some of the bug fixes to next and ima-evm-utils-
1.2.y. Which of your remaining patches are bug fixes and should be
applied to both branches?
thanks,
Mimi
next prev parent reply other threads:[~2019-07-30 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190729101252.iirdsz2j5bjk267f@altlinux.org>
2019-07-30 6:26 ` ima-evm-utils: git tagging for release Vitaly Chikunov
2019-07-30 11:30 ` Mimi Zohar
2019-07-30 14:36 ` Mimi Zohar [this message]
2019-07-30 15:28 ` Vitaly Chikunov
2019-07-30 17:08 ` Mimi Zohar
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=1564497374.4189.84.camel@kernel.org \
--to=zohar@kernel.org \
--cc=bmeneg@redhat.com \
--cc=dbaryshkov@gmail.com \
--cc=linux-integrity@vger.kernel.org \
--cc=pvorel@suse.cz \
--cc=vt@altlinux.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).