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: Sun, 11 Oct 2015 23:03:00 -0000	[thread overview]
Message-ID: <bug-11460-131-WKaAs6cVn0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11460-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=11460

Dmitry V. Levin <ldv at altlinux dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ldv at altlinux dot org
           Assignee|ldv at altlinux dot org            |mjw at redhat dot com

--- Comment #4 from Dmitry V. Levin <ldv at altlinux dot org> ---
(In reply to Mark Wielaard from comment #3)
> Posted a patch: https://sourceware.org/ml/libc-alpha/2015-10/msg00309.html

Thanks!

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-10-11 23:03 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
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 [this message]
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-WKaAs6cVn0@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).