From: Eric Biggers <ebiggers@kernel.org>
To: Jes Sorensen <jes.sorensen@gmail.com>
Cc: linux-fscrypt@vger.kernel.org, kernel-team@fb.com,
Jes Sorensen <jsorensen@fb.com>
Subject: Re: [PATCH v2 0/2] fsverity-utils Makefile fixes
Date: Wed, 20 May 2020 14:03:35 -0700 [thread overview]
Message-ID: <20200520210335.GA218475@gmail.com> (raw)
In-Reply-To: <20200520200811.257542-1-Jes.Sorensen@gmail.com>
On Wed, May 20, 2020 at 04:08:09PM -0400, Jes Sorensen wrote:
> From: Jes Sorensen <jsorensen@fb.com>
>
> Hi
>
> This addresses the comments to the previous version of these Makefile
> changes.
>
> Let me know if you have any additional issues with it?
>
> I'd really love to see an official release soon that includes these
> changes, which I can point to when submitting the RPM patches. Any
> chance of doing 1.1 or something like that?
>
> Cheers,
> Jes
I'll release v1.1 after I merge the libfsverity patches, but I need to look over
everything again first before committing to a stable API. I'll try to get to it
this weekend; I'm also busy with a lot of other things.
Also, could you look over my patches and leave your Reviewed-by? I expected
that you'd have a few more comments.
- Eric
next prev parent reply other threads:[~2020-05-20 21:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 20:08 [PATCH v2 0/2] fsverity-utils Makefile fixes Jes Sorensen
2020-05-20 20:08 ` [PATCH 1/2] Fix Makefile to delete objects from the library on make clean Jes Sorensen
2020-05-20 20:08 ` [PATCH 2/2] Let package manager override CFLAGS and CPPFLAGS Jes Sorensen
2020-05-20 21:06 ` Eric Biggers
2020-05-20 21:20 ` Jes Sorensen
2020-05-20 21:03 ` Eric Biggers [this message]
2020-05-20 21:04 ` [PATCH v2 0/2] fsverity-utils Makefile fixes Jes Sorensen
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=20200520210335.GA218475@gmail.com \
--to=ebiggers@kernel.org \
--cc=jes.sorensen@gmail.com \
--cc=jsorensen@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-fscrypt@vger.kernel.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 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.