public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sourceware.org@jan-o-sch.net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/15312] SEEK_HOLE and SEEK_DATA not exported as expected Date: Wed, 27 Mar 2013 15:05:00 -0000 [thread overview] Message-ID: <bug-15312-131-vF4BNLUtIu@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15312-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15312 --- Comment #2 from Jan Schmidt <sourceware.org@jan-o-sch.net> 2013-03-27 15:04:55 UTC --- So you really want a user space app to include <linux/fs.h> directly!? -- 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-03-27 15:05 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-27 14:28 [Bug libc/15312] New: " sourceware.org@jan-o-sch.net 2013-03-27 14:50 ` [Bug libc/15312] " aj at suse dot de 2013-03-27 15:05 ` sourceware.org@jan-o-sch.net [this message] 2013-03-27 15:12 ` aj at suse dot de 2013-03-27 17:55 ` sourceware.org@jan-o-sch.net 2013-03-27 20:51 ` mtk.manpages at gmail dot com 2014-06-13 18:35 ` fweimer at redhat 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-15312-131-vF4BNLUtIu@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: linkBe 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).