bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: bug-gnulib@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: [PATCH 1/2] Document lseek SEEK_DATA/SEEK_HOLE
Date: Sun, 23 Jun 2019 15:41:29 -0700	[thread overview]
Message-ID: <20190623224130.15756-1-eggert@cs.ucla.edu> (raw)

* doc/posix-functions/lseek.texi (lseek):
Document some systems that do not support SEEK_DATA and SEEK_HOLE.
---
 ChangeLog                      | 6 ++++++
 doc/posix-functions/lseek.texi | 3 +++
 2 files changed, 9 insertions(+)

diff --git a/ChangeLog b/ChangeLog
index cdc2b3d7a..cf0bbb396 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2019-06-23  Paul Eggert  <eggert@cs.ucla.edu>
+
+	Document lseek SEEK_DATA/SEEK_HOLE
+	* doc/posix-functions/lseek.texi (lseek):
+	Document some systems that do not support SEEK_DATA and SEEK_HOLE.
+
 2019-06-22  Akim Demaille  <akim@lrde.epita.fr>
 
 	argmatch: put all the docs member last.
diff --git a/doc/posix-functions/lseek.texi b/doc/posix-functions/lseek.texi
index 813bdd9b6..b4d03f528 100644
--- a/doc/posix-functions/lseek.texi
+++ b/doc/posix-functions/lseek.texi
@@ -31,4 +31,7 @@ When the @code{lseek} function fails, POSIX says that the file offset remains
 unchanged.  But on some platforms, attempting to set a negative file offset
 fails and sets the file offset to 0:
 BeOS.
+@item
+Some systems do not support @code{SEEK_DATA} and @code{SEEK_HOLE}:
+AIX, HP-UX, Microsoft Windows, NetBSD, OpenBSD.
 @end itemize
-- 
2.21.0



             reply	other threads:[~2019-06-23 22:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-23 22:41 Paul Eggert [this message]
2019-06-23 22:41 ` [PATCH 2/2] Document setvbuf _IOLBF problem Paul Eggert

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

  List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190623224130.15756-1-eggert@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=bug-gnulib@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).