Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 52518 invoked from network); 9 Dec 2004 10:10:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 9 Dec 2004 10:10:19 -0000 Received: (qmail 19061 invoked by uid 500); 9 Dec 2004 10:09:46 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 19021 invoked by uid 500); 9 Dec 2004 10:09:45 -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 18999 invoked by uid 99); 9 Dec 2004 10:09:45 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Message-ID: <41B82484.7000009@xbc.nu> Date: Thu, 09 Dec 2004 11:10:12 +0100 From: =?UTF-8?B?QnJhbmtvIMSMaWJlag==?= User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ingo Weinhold Cc: APR Dev Subject: Re: BeOS specific patches References: <20041208231327.4735.2@cs.tu-berlin.de> In-Reply-To: <20041208231327.4735.2@cs.tu-berlin.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at amis.net X-Spam-Status: No, hits=-2.586 required=5 tests=AWL, BAYES_00 X-Spam-Level: X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Ingo Weinhold wrote: >Howdy, > >I've invested some time to fix a couple of problems under BeOS and am about >to prepare the patches. The APR home page says that patches can be sent to >the list, but since I haven't seen any since I'm subscribed (bit more than >a week), I thought, I rather ask. > > Certainly it's O.K. to send patches to the list. >I have worked with release 1.0.1 source base. Is it OK to send diffs >against this version or shall build ones against some SVN version? > > It's best if you send in patches against SVN trunk (the tip of the mainline); just "svn checkout" apr/trunk, make your changes in the working copy, then "svn diff" to create the patch. -- Brane