From: Nix <nix@esperi.org.uk>
To: "Michael Kerrisk" <mtk-manpages@gmx.net>
Cc: mingo@elte.hu, mpm@selenic.com, linux-kernel@vger.kernel.org,
michael.kerrisk@gmx.net, akpm@osdl.org, chrisw@osdl.org
Subject: Re: Broke nice range for RLIMIT NICE
Date: Fri, 29 Jul 2005 21:57:48 +0100 [thread overview]
Message-ID: <871x5hgwj7.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <12213.1122650084@www71.gmx.net> (Michael Kerrisk's message of "Fri, 29 Jul 2005 17:14:44 +0200 (MEST)")
On Fri, 29 Jul 2005, Michael Kerrisk uttered the following:
>> On 29 Jul 2005, Michael Kerrisk stated:
>> > Yes, as noted in my earlier message -- at the moment RLIMIT_NICE
>> > still isn't in the current glibc snapshot...
>>
>> According to traffic on libc-hacker, Ulrich committed it on Jun 20
>> (along with RLIMIT_RTPRIO support).
>
> I (now) see the message that you mean on libc-hacker, nevertheless,
> looking at the glibc-2.3-20050725 snapshot, these two constants do
> not appear anywhere. (Strange!)
That just means it hasn't gone into the stable branch (yet?); since
that's bugfix-only and changes are bursted in intermittently by Roland,
that's not very surprising.
But if you look in HEAD (2.4-to-be), you'll see it.
--
`Tor employs several thousand editors who they keep in dank
subterranean editing facilities not unlike Moria' -- James Nicoll
next prev parent reply other threads:[~2005-07-29 20:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 15:04 Broke nice range for RLIMIT NICE Michael Kerrisk
2005-07-28 17:43 ` Andrew Morton
2005-07-29 11:29 ` [PATCH] MAINTAINERS record -- MAN-PAGES Michael Kerrisk
2005-07-29 6:13 ` Broke nice range for RLIMIT NICE Matt Mackall
2005-07-29 8:38 ` Ingo Molnar
2005-07-29 10:42 ` Michael Kerrisk
2005-07-29 14:50 ` Nix
2005-07-29 15:14 ` Michael Kerrisk
2005-07-29 20:57 ` Nix [this message]
2005-07-29 10:40 ` Michael Kerrisk
2005-07-29 20:18 ` Chris Wright
2005-07-29 20:51 ` Chris Wright
2005-07-29 21:02 ` Lee Revell
2005-07-29 21:07 ` Chris Wright
2005-08-15 20:13 ` [PATCH] Fix " Matt Mackall
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=871x5hgwj7.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.kerrisk@gmx.net \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=mtk-manpages@gmx.net \
/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