From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: [PATCH] chmodat, chownat: new modules
Date: Sat, 22 Feb 2020 23:47:22 +0100 [thread overview]
Message-ID: <1822910.auxUVqHv6o@omega> (raw)
In-Reply-To: <20200222201039.349826-1-eggert@cs.ucla.edu>
Paul Eggert wrote:
> These are split from fchmodat, fchownat. GNU Emacs needs the
> POSIX-specified fchmodat, but not the gnulib-specified chmodat and
> lchmodat. Split the latter two into a new module chmodat.
As this is a backward-incompatible change for the gnulib users, we
should advertise it in the NEWS file. Done like this:
2020-02-22 Bruno Haible <bruno@clisp.org>
Update NEWS.
* NEWS: Mention the last change.
diff --git a/NEWS b/NEWS
index bc81dfc..4b9a983 100644
--- a/NEWS
+++ b/NEWS
@@ -58,6 +58,16 @@ User visible incompatible changes
Date Modules Changes
+2020-02-22 fchownat This module no longer defines the functions
+ 'chownat' and 'lchownat'. Program that need these
+ functions should add the module 'chownat' to the
+ list of imported modules.
+
+2020-02-22 fchmodat This module no longer defines the functions
+ 'chmodat' and 'lchmodat'. Program that need these
+ functions should add the module 'chmodat' to the
+ list of imported modules.
+
2020-02-07 fchmodat When applied to non-symlinks, these now act like
lchmod chmod (the BSD behavior, which POSIX requires for
fchmodat + AT_SYMLINK_NOFOLLOW), instead of failing
next prev parent reply other threads:[~2020-02-22 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 20:10 [PATCH] chmodat, chownat: new modules Paul Eggert
2020-02-22 22:47 ` Bruno Haible [this message]
2020-02-25 14:23 ` Pádraig Brady
2020-02-25 16:11 ` Bruno Haible
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=1822910.auxUVqHv6o@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
/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).