From ebf20cddae622426cf525caa63918ac45f244809 Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Thu, 9 May 2019 09:43:55 +0200 Subject: [PATCH] Changes: Expanded tabs --- Changes | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/Changes b/Changes index b46ffbf46..178b4cc2b 100644 --- a/Changes +++ b/Changes @@ -142,18 +142,18 @@ tee.2 fopen.3 Elliot Hughes Explain BSD vs glibc "a+" difference - Where is the initial read position for an "a+" stream? + Where is the initial read position for an "a+" stream? - POSIX leaves this unspecified. Most BSD man pages are silent, and - MacOS has the ambiguous "The stream is positioned at the end of - the file", not differentiating between reads and writes other than - to say that fseek(3) does not affect writes. glibc's documentation - explicitly specifies that the initial read position is the - beginning of the file. + POSIX leaves this unspecified. Most BSD man pages are silent, and + MacOS has the ambiguous "The stream is positioned at the end of + the file", not differentiating between reads and writes other than + to say that fseek(3) does not affect writes. glibc's documentation + explicitly specifies that the initial read position is the + beginning of the file. - My new wording is based on the BSD implementations, so you may - prefer to replace the non-glibc section with "unspecified", or - indeed remove all claims about the initial read position. + My new wording is based on the BSD implementations, so you may + prefer to replace the non-glibc section with "unspecified", or + indeed remove all claims about the initial read position. mallinfo.3 Elliott Hughes