summaryrefslogtreecommitdiff
path: root/lib/utimens.c
diff options
context:
space:
mode:
authorBruno Haible <bruno@clisp.org>2017-09-14 00:35:56 +0200
committerBruno Haible <bruno@clisp.org>2017-09-14 00:35:56 +0200
commit03eac9d394567d707a74826dfc9c305555946597 (patch)
treedf5743f58e2f39dd8ad3b30da118b3afad285c9e /lib/utimens.c
parentb7773f3f796588544f36b45be274f42b36b42149 (diff)
downloadgnulib-03eac9d394567d707a74826dfc9c305555946597.tar.gz
all: Replace many more http URLs by https URLs. Update stale URLs.
* users.txt: Remove mention of 'newts'. * lib/localename.c: Update comment about LANG_SOTHO.
Diffstat (limited to 'lib/utimens.c')
-rw-r--r--lib/utimens.c10
1 files changed, 5 insertions, 5 deletions
diff --git a/lib/utimens.c b/lib/utimens.c
index a5716ac810..55545e8ce9 100644
--- a/lib/utimens.c
+++ b/lib/utimens.c
@@ -196,7 +196,7 @@ fdutimens (int fd, char const *file, struct timespec const timespec[2])
/* Some Linux-based NFS clients are buggy, and mishandle timestamps
of files in NFS file systems in some cases. We have no
configure-time test for this, but please see
- <http://bugs.gentoo.org/show_bug.cgi?id=132673> for references to
+ <https://bugs.gentoo.org/show_bug.cgi?id=132673> for references to
some of the problems with Linux 2.6.16. If this affects you,
compile with -DHAVE_BUGGY_NFS_TIME_STAMPS; this is reported to
help in some cases, albeit at a cost in performance. But you
@@ -250,8 +250,8 @@ fdutimens (int fd, char const *file, struct timespec const timespec[2])
result = utimensat (AT_FDCWD, file, ts, 0);
# ifdef __linux__
/* Work around a kernel bug:
- http://bugzilla.redhat.com/442352
- http://bugzilla.redhat.com/449910
+ https://bugzilla.redhat.com/show_bug.cgi?id=442352
+ https://bugzilla.redhat.com/show_bug.cgi?id=449910
It appears that utimensat can mistakenly return 280 rather
than -1 upon ENOSYS failure.
FIXME: remove in 2010 or whenever the offending kernels
@@ -566,8 +566,8 @@ lutimens (char const *file, struct timespec const timespec[2])
result = utimensat (AT_FDCWD, file, ts, AT_SYMLINK_NOFOLLOW);
# ifdef __linux__
/* Work around a kernel bug:
- http://bugzilla.redhat.com/442352
- http://bugzilla.redhat.com/449910
+ https://bugzilla.redhat.com/show_bug.cgi?id=442352
+ https://bugzilla.redhat.com/show_bug.cgi?id=449910
It appears that utimensat can mistakenly return 280 rather
than -1 upon ENOSYS failure.
FIXME: remove in 2010 or whenever the offending kernels