From: Pavel Machek <pavel@ucw.cz>
To: Karel Zak <kzak@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.36
Date: Sat, 25 Jul 2020 19:02:11 +0200 [thread overview]
Message-ID: <20200725170211.GA2807@amd> (raw)
In-Reply-To: <20200723100828.262ftx3qhie2sc32@ws.net.home>
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
Hi!
> The commands fdisk(8), sfdisk(8), cfdisk(8), mkswap(8) and wipefs(8) now
> support block devices locking by flock(2) to better behave with udevd or other
> tools. Ffor more details see https://systemd.io/BLOCK_DEVICE_LOCKING/. This
There's typo "ffor", but I guess it is too late to fix that?
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2020-07-25 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 10:08 [ANNOUNCE] util-linux v2.36 Karel Zak
2020-07-25 17:02 ` Pavel Machek [this message]
2020-08-07 11:51 ` Karel Zak
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=20200725170211.GA2807@amd \
--to=pavel@ucw.cz \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 NNTP newsgroup(s).