This is the mail archive of the
cygwin-patches@sources.redhat.com
mailing list for the Cygwin project.
Re: Patch to make setrlimit() more forgiving
- To: Dave Sainty <dave at dtsp dot co dot nz>
- Subject: Re: Patch to make setrlimit() more forgiving
- From: Chris Faylor <cgf at redhat dot com>
- Date: Fri, 5 Jan 2001 11:17:29 -0500
- Cc: cygwin-patches at cygwin dot com
- References: <20010104214112.A32564@redhat.com> <200101050922.f059MVD30284@mail.redhat.com>
- Reply-To: cygwin-patches at cygwin dot com
On Fri, Jan 05, 2001 at 10:23:28PM +1300, Dave Sainty wrote:
>Christopher Faylor writes:
>
>> It looks good but I need a ChangeLog.
>>
>> cgf
>>
>> On Fri, Jan 05, 2001 at 03:38:43PM +1300, David Sainty wrote:
>> >Attached is a simple patch that prevents setrlimit() failing with an error
>> >when the operation would not have changed anything. This allows all
>> >resource types to be set, so long as the setting is identical to the current
>> >pseudo-settings.
>
>Certainly :) Sorry, I'm sure there was some FAQ I was meant to read
>before posting patches :)
>
>Fri Jan 5 15:38:43 2001 Dave Sainty <david.sainty@dtsp.co.nz>
>
> * resource.cc: Allow all null setrlimit() operations to succeed
I don't know if there is, but you should probably check the archives for
the correct format of a ChangeLog. This is also mentioned at
www.gnu.org, somewhere. Submitting a ChangeLog with a patch is a pretty
standard net procedure.
This is almost correct, but if you look at the current Cygwin ChangeLog,
you can see that it is missing a function name and a period.
I'll add those and check this in.
cgf