From d5dd3a91dcd61ab5aacec0a4278469e100640676 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Fri, 26 Feb 2010 05:45:27 +0100 Subject: [PATCH] Removed trailing white space at end of lines --- man2/fcntl.2 | 2 +- man2/setreuid.2 | 2 +- man2/sync_file_range.2 | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/man2/fcntl.2 b/man2/fcntl.2 index 03fa133b1..c51b705c3 100644 --- a/man2/fcntl.2 +++ b/man2/fcntl.2 @@ -673,7 +673,7 @@ Any other value (including is the signal to send instead, and in this case additional info is available to the signal handler if installed with .BR SA_SIGINFO . -.\" +.\" .\" The following was true only up until 2.6.11: .\" .\" Additionally, passing a nonzero value to diff --git a/man2/setreuid.2 b/man2/setreuid.2 index 530a4d020..034a193f8 100644 --- a/man2/setreuid.2 +++ b/man2/setreuid.2 @@ -118,7 +118,7 @@ POSIX.1 does not specify all of possible ID changes that are permitted on Linux for an unprivileged process. For .BR setreuid (), -the effective user ID can be made the same as the +the effective user ID can be made the same as the real user ID or the save set-user-ID, and it is unspecified whether unprivileged processes may set the real user ID to the real user ID, the effective user ID, or the diff --git a/man2/sync_file_range.2 b/man2/sync_file_range.2 index cb4b8e312..cb0fee13d 100644 --- a/man2/sync_file_range.2 +++ b/man2/sync_file_range.2 @@ -88,7 +88,7 @@ Therefore, unless the application is strictly performing overwrites of already-instantiated disk blocks, there are no guarantees that the data will be available after a crash. There is no user interface to know if a write is purely an overwrite. -On filesystem using copy-on-write semantics (e.g., +On filesystem using copy-on-write semantics (e.g., .IR btrfs ) an overwrite of existing allocated blocks is impossible. When writing into preallocated space,