public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ldv at altlinux dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/11460] fts has no LFS support
Date: Fri, 11 Jan 2013 01:14:00 -0000 [thread overview]
Message-ID: <bug-11460-131-mKrmU6gudu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11460-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=11460
Dmitry V. Levin <ldv at altlinux dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|unassigned at sourceware |ldv at altlinux dot org
|dot org |
--- Comment #1 from Dmitry V. Levin <ldv at altlinux dot org> 2013-01-11 01:14:00 UTC ---
The only reasonable explanation for the fact that fts functions have no LFS
support while related ftw functions have LFS support is that nobody has
proposed a patch yet.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-01-11 1:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11460-131@http.sourceware.org/bugzilla/>
2012-12-19 10:44 ` schwab@linux-m68k.org
2013-01-11 1:14 ` ldv at altlinux dot org [this message]
2014-06-30 18:19 ` fweimer at redhat dot com
2015-08-24 9:45 ` jsm28 at gcc dot gnu.org
2015-10-09 16:31 ` jistone at redhat dot com
2015-10-11 0:09 ` mjw at redhat dot com
2015-10-11 22:51 ` mjw at redhat dot com
2015-10-11 23:03 ` ldv at altlinux dot org
2024-02-06 19:15 ` gabravier at gmail dot com
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=bug-11460-131-mKrmU6gudu@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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).