mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Dominique Martinet <dominique.martinet@atmark-techno.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] [PATCH] nftw: implement FTW_ACTIONRETVAL
Date: Mon, 12 Apr 2021 10:17:30 -0400	[thread overview]
Message-ID: <20210412141729.GL2546@brightrain.aerifal.cx> (raw)
In-Reply-To: <20210326054456.899700-1-dominique.martinet@atmark-techno.com>

On Fri, Mar 26, 2021 at 02:44:56PM +0900, Dominique Martinet wrote:
> nftw is sometimes used with e.g. FTW_SKIP_SUBTREE on linux which
> requires special handling.
> 
> A similar patch was sent in 2018[1] and general feedbacks for nftw
> seemed positive, but the original work's license was not clear so this
> implementation was made without using it, looking at the linux man page
> and comparing with glibc's behaviour through test programs.
> 
> [1] https://www.openwall.com/lists/musl/2018/12/16/1

Feedback for that submission as a whole was negative because it was
just "throw in everything I found that systemd wanted", which is a
policy discussion that's already been had and the answer is no.
However that's not a judgement on any individual feature like
FTW_ACTIONRETVAL, which could meet criteria for inclusion. I haven't
gotten a good chance to look at this yet, but if you haven't already,
could you post some supporting reasons for this (like widespread usage
by applications that you've found)? That would help determine if it's
appropriate.

Rich

  parent reply	other threads:[~2021-04-12 14:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26  5:44 Dominique Martinet
2021-04-12  5:53 ` [musl] " Dominique Martinet
2021-04-12  6:09 ` [musl] " Ariadne Conill
2021-04-12  6:45   ` Dominique Martinet
2021-04-12 14:17 ` Rich Felker [this message]
2021-04-12 23:25   ` Dominique Martinet

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

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

  git send-email \
    --in-reply-to=20210412141729.GL2546@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=dominique.martinet@atmark-techno.com \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).