linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] fts.3 is not available in LFS builds
Date: Wed, 19 Mar 2014 14:29:42 +0100	[thread overview]
Message-ID: <53299BC6.1000905@gmail.com> (raw)
In-Reply-To: <8628933.tn1CQP9rHn@vapier>

On 03/19/2014 06:56 AM, Mike Frysinger wrote:
> On Tue 18 Mar 2014 23:12:45 Mike Frysinger wrote:
>> maybe we just ignore the issue since fts.h is dead anyways ?  just add a
>> section to the fts(3) page recommending people use ftw(3) instead ?
> 
> i might be completely off on fts vs ftw.  there's discussion on glibc lists 
> about maybe fixing fts to not suck.  perhaps we just link to the existing bug 
> on the topic ?
> https://sourceware.org/bugzilla/show_bug.cgi?id=11460

Who knows what'll happen. I put a link to that bug in the page source.

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-03-19 13:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-15 13:54 [PATCH] fts.3 is not available in LFS builds Christoph Hellwig
     [not found] ` <20140315135416.GA10430-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-03-15 14:47   ` Michael Kerrisk (man-pages)
     [not found]     ` <CAKgNAkgqXUf0yWaXyAD7yBJgivp9Jmwvz4EAnh_DpyActuoGwA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-16 17:22       ` Christoph Hellwig
     [not found]         ` <20140316172219.GA16900-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-03-17 13:56           ` Michael Kerrisk (man-pages)
     [not found]             ` <5326FF14.7010305-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-17 14:01               ` Christoph Hellwig
     [not found]                 ` <20140317140118.GA11576-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-03-17 14:02                   ` Michael Kerrisk (man-pages)
     [not found]                     ` <CAKgNAkh7ES18jT2coD39ZXvjUxkrZavaG=SufNS_-16SgM3kUg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-17 14:06                       ` Christoph Hellwig
     [not found]                         ` <20140317140616.GA15958-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-03-17 14:11                           ` Michael Kerrisk (man-pages)
     [not found]                             ` <CAKgNAkinnsvoXT_FNxaS7L5Umo6va8OCVnTv-gZ5vvVSFi2--w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-19  3:12                               ` Mike Frysinger
2014-03-19  5:56                                 ` Mike Frysinger
2014-03-19 13:29                                   ` Michael Kerrisk (man-pages) [this message]
2014-03-19 13:29                                 ` Michael Kerrisk (man-pages)

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=53299BC6.1000905@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.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 NNTP newsgroup(s).