From: Karel Zak <kzak@redhat.com>
To: Ian Kent <raven@themaw.net>
Cc: util-linux <util-linux@vger.kernel.org>,
John Westerdale <jwesterd@redhat.com>,
fhirtz@redhat.com
Subject: Re: [PATCH v2] libmount: use autofs mount hint to ignore autofs mount entries
Date: Tue, 29 Nov 2022 11:16:00 +0100 [thread overview]
Message-ID: <20221129101600.bzxikojw7chglrjw@ws.net.home> (raw)
In-Reply-To: <166928005898.283308.14145999397636040618.stgit@donald.themaw.net>
On Thu, Nov 24, 2022 at 04:54:19PM +0800, Ian Kent wrote:
> libmount/src/context.c | 24 ++++++++++++++++++++++++
> libmount/src/libmount.h.in | 2 ++
> libmount/src/libmount.sym | 3 +++
> libmount/src/mountP.h | 7 ++++++-
> libmount/src/tab_parse.c | 34 ++++++++++++++++++++++++++++++++++
> 5 files changed, 69 insertions(+), 1 deletion(-)
Applied, thanks!
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2022-11-29 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 8:54 [PATCH v2] libmount: use autofs mount hint to ignore autofs mount entries Ian Kent
2022-11-29 10:16 ` Karel Zak [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=20221129101600.bzxikojw7chglrjw@ws.net.home \
--to=kzak@redhat.com \
--cc=fhirtz@redhat.com \
--cc=jwesterd@redhat.com \
--cc=raven@themaw.net \
--cc=util-linux@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).