From: Yuri Kozlov <yuray-YPGtXv8QU+00kPtPmH8OGQ@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: small improvement for st.4
Date: Sat, 31 Jul 2010 14:49:09 +0400 [thread overview]
Message-ID: <20100731144909.528c8104@keeper.home.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
Hello.
--- man-pages-git/man4/st.4 2010-03-26 17:46:41.000000000 +0300
+++ /tmp/st.4 2010-07-31 14:48:15.000000000 +0400
@@ -490,6 +490,7 @@
If this option is false and the drive uses a fixed block size, then
all write operations must be for a multiple of the block size.
This option must be set false to write reliable multivolume archives.
+.TP
.BR MT_ST_ASYNC_WRITES " (Default: true)"
When this option is true, write operations return immediately without
waiting for the data to be transferred to the drive if the data fits
--
Best Regards,
Yuri Kozlov
[-- Attachment #2: st.4.patch --]
[-- Type: text/x-patch, Size: 527 bytes --]
--- man-pages-git/man4/st.4 2010-03-26 17:46:41.000000000 +0300
+++ /tmp/st.4 2010-07-31 14:48:15.000000000 +0400
@@ -490,6 +490,7 @@
If this option is false and the drive uses a fixed block size, then
all write operations must be for a multiple of the block size.
This option must be set false to write reliable multivolume archives.
+.TP
.BR MT_ST_ASYNC_WRITES " (Default: true)"
When this option is true, write operations return immediately without
waiting for the data to be transferred to the drive if the data fits
next reply other threads:[~2010-07-31 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 10:49 Yuri Kozlov [this message]
[not found] ` <20100731144909.528c8104-CpVCSV+zb/Ftei/ch0jEm2ZHpeb/A1Y/@public.gmane.org>
2010-08-29 4:35 ` small improvement for st.4 Michael Kerrisk
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=20100731144909.528c8104@keeper.home.local \
--to=yuray-ypgtxv8qu+00kptpmh8ogq@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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