From: Phillip Potter <phil@philpotter.co.uk>
To: David Sterba <dsterba@suse.cz>
Cc: ooo@electrozaur.com, linux-fsdevel@vger.kernel.org
Subject: Re: Re-ack of exofs patch for common file type conversion
Date: Wed, 31 Oct 2018 09:19:44 +0000 [thread overview]
Message-ID: <20181031091944.GB19486@pathfinder> (raw)
In-Reply-To: <20181030185604.GG9136@twin.jikos.cz>
On Tue, Oct 30, 2018 at 07:56:04PM +0100, David Sterba wrote:
> On Sat, Oct 27, 2018 at 01:59:07AM +0100, Phillip Potter wrote:
> > Dear Boaz,
> >
> > Rather than just keeping your ACK on the latest patch, it has changed
> > ever so slightly so I wandered if you would mind reviewing and seeing
> > if you are still ok with it? Many thanks.
>
> FYI, exofs is probably on the way out, see
>
> https://lore.kernel.org/lkml/20181027082019.20838-1-hch@lst.de/
Dear David,
Thanks, I shall watch closely and republish without this patch in that case.
Regards,
Phil
prev parent reply other threads:[~2018-10-31 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 0:59 Re-ack of exofs patch for common file type conversion Phillip Potter
2018-10-30 18:56 ` David Sterba
2018-10-31 9:19 ` Phillip Potter [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=20181031091944.GB19486@pathfinder \
--to=phil@philpotter.co.uk \
--cc=dsterba@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ooo@electrozaur.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.
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).