From: "Linux NILFS <linuxnilfs@gmail.com>" <linuxnilfs@gmail.com>
To: linux-nilfs@vger.kernel.org
Subject: NILFS utils 2.2.11 was released
Date: Wed, 3 Apr 2024 09:17:33 -0700 [thread overview]
Message-ID: <CAE7Udf-raBq4Gn=2zCVWA9Psb-LfeKXZ6UGH4=C70hHpaPg7QQ@mail.gmail.com> (raw)
A maintenance release that includes a bug fix regarding escape
characters in mount table parsing
from https://nilfs.sourceforge.io/en/download.html#2.2.11-u
reply other threads:[~2024-04-03 16:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAE7Udf-raBq4Gn=2zCVWA9Psb-LfeKXZ6UGH4=C70hHpaPg7QQ@mail.gmail.com' \
--to=linuxnilfs@gmail.com \
--cc=linux-nilfs@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).