From dev-return-12588-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Thu Aug 12 21:16:34 2004
Return-Path:
Delivered-To: apmail-apr-dev-archive@www.apache.org
Received: (qmail 87236 invoked from network); 12 Aug 2004 21:16:34 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
by minotaur-2.apache.org with SMTP; 12 Aug 2004 21:16:34 -0000
Received: (qmail 50822 invoked by uid 500); 12 Aug 2004 21:16:27 -0000
Delivered-To: apmail-apr-dev-archive@apr.apache.org
Received: (qmail 50523 invoked by uid 500); 12 Aug 2004 21:16:25 -0000
Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
List-Post:
List-Help:
List-Unsubscribe:
List-Subscribe:
Delivered-To: mailing list dev@apr.apache.org
Received: (qmail 50502 invoked by uid 99); 12 Aug 2004 21:16:25 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
tests=FORGED_RCVD_HELO
X-Spam-Check-By: apache.org
Errors-To:
Message-Id: <6.1.2.0.2.20040812155314.12b4c8c8@pop3.rowe-clan.net>
X-Sender: wrowe%rowe-clan.net@pop3.rowe-clan.net
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Thu, 12 Aug 2004 15:58:16 -0500
To: "James Mansion"
From: "William A. Rowe, Jr."
Subject: Re: Win32 critsec
Cc:
In-Reply-To:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N
At 02:49 PM 8/12/2004, James Mansion wrote:
>I'd like to offer a replacement for the broken critsec code.
>
>Who can I send it to for review?
>
>I've never contributed before, have filled no paperwork etc. I work through
>a contractor umbrella company and I'm at home rather than at a client site,
>so I don't think theer will be a problem getting paperwork - just a delay
>since I'm not a director etc.
Feel free to post your patches to the list, and/or attach them to the
appropriate bug report with the PatchAvailable keyword. Both is probably
the surest way that they are considered. We prefer diff -u3 style patches,
following the style guide http://www.apache.org/dev/styleguide.html
If this is a trivial bugfix, we don't require a CLA. If you are providing an
entirely new implementation, or submitting brand new code, we would ask
you to submit a Contributors License Agreement, and if you don't have
full authority to speak for what you do on your companies' time, also file
the Corp CLA... http://www.apache.org/licenses/#clas
Instructions for faxing or mailing these documents is embedded in the
agreements themselves.
Please remember, the more focused and single purpose each patch
you offer is, the easier it is for the reviewers to grok and approve/commit.
Looking forward to your contributions!
Bill