[Bug manual/19086] posix_fallocate64 documented argument order is wrong.

[Bug manual/19086] posix_fallocate64 documented argument order is wrong.

[cvs-commit at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=19086

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  b86b4f5ef2fd801b1269938747a438838f1545c1 (commit)
      from  119d073e334e9889a3fd904b333cd13d8217bc58 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b86b4f5ef2fd801b1269938747a438838f1545c1

commit b86b4f5ef2fd801b1269938747a438838f1545c1
Author: Carlos O'Donell <carlos@systemhalted.org>
Date:   Wed Oct 7 14:10:43 2015 -0400

    Fix manual argument order for posix_fallocate64 (Bug 19086).

    The argument order for posix_fallocate64 in the manual
    was wrong, it was listed as [fd, len, offset] when it
    should have been [fd, offset, len].

    Verified io/fcntl.h has the right argument order, and it
    does. Verified generated PDF.

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog           |    6 ++++++
 manual/filesys.texi |    2 +-
 2 files changed, 7 insertions(+), 1 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug manual/19086] posix_fallocate64 documented argument order is wrong.

[carlos at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=19086

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |2.23

--- Comment #2 from Carlos O'Donell <carlos at redhat dot com> ---
Fixed for 2.23.

-- 
You are receiving this mail because:
You are on the CC list for the bug.