From: Jakub Jelinek <jakub@redhat.com>
To: Thorsten Kukuk <kukuk@suse.de>
Cc: libc-hacker@sourceware.cygnus.com
Subject: Re: [PATCH] more setrlimit for 2.1
Date: Mon, 24 Jan 2000 07:09:00 -0000 [thread overview]
Message-ID: <20000124161357.H2708@mff.cuni.cz> (raw)
In-Reply-To: <20000124160522.A13149@Wotan.suse.de>
On Mon, Jan 24, 2000 at 04:05:22PM +0100, Thorsten Kukuk wrote:
>
> Hi,
>
> In syscalls.list, the old[sg]etrlimit must be removed, too.
I still wonder if it would not be better to use signed rlim_t in 2.1.3.
And we have to s/GLIBC_2.1.3/GLIBC_2.2/ *rlimit* symbols in 2.1.90, because
it will be otherwise rather confusing (e.g. for rpm dependencies).
Cheers,
Jakub
___________________________________________________________________
Jakub Jelinek | jakub@redhat.com | http://sunsite.mff.cuni.cz/~jj
Linux version 2.3.41 on a sparc64 machine (1343.49 BogoMips)
___________________________________________________________________
prev parent reply other threads:[~2000-01-24 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-24 7:05 Thorsten Kukuk
2000-01-24 7:09 ` Jakub Jelinek [this message]
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=20000124161357.H2708@mff.cuni.cz \
--to=jakub@redhat.com \
--cc=kukuk@suse.de \
--cc=libc-hacker@sourceware.cygnus.com \
/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).