From: Andrey Albershteyn <aalbersh@redhat.com>
To: linux-xfs@vger.kernel.org
Cc: aalbersh@kernel.org, Andrey Albershteyn <aalbersh@redhat.com>
Subject: [PATCH v3 0/2] Minor fixes for xfsprogs
Date: Wed, 2 Oct 2024 12:36:22 +0200 [thread overview]
Message-ID: <20241002103624.1323492-1-aalbersh@redhat.com> (raw)
Hi,
These two patches are fix for building xfsprogs in immutable distros
and update to .gitignore.
v3:
- Use wildcard or backup files
v2:
- Use wildcard for scrub systemd/cron files
Andrey Albershteyn (2):
xfsprogs: fix permissions on files installed by libtoolize
xfsprogs: update gitignore
.gitignore | 12 ++++++++----
Makefile | 2 ++
2 files changed, 10 insertions(+), 4 deletions(-)
--
2.44.1
next reply other threads:[~2024-10-02 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 10:36 Andrey Albershteyn [this message]
2024-10-02 10:36 ` [PATCH v3 1/2] xfsprogs: fix permissions on files installed by libtoolize Andrey Albershteyn
2024-10-02 22:54 ` Darrick J. Wong
2024-10-02 10:36 ` [PATCH v3 2/2] xfsprogs: update gitignore Andrey Albershteyn
2024-10-02 22:54 ` Darrick J. Wong
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=20241002103624.1323492-1-aalbersh@redhat.com \
--to=aalbersh@redhat.com \
--cc=aalbersh@kernel.org \
--cc=linux-xfs@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 NNTP newsgroup(s).