Return-Path: Delivered-To: apmail-jakarta-lucene-dev-archive@apache.org Received: (qmail 71391 invoked from network); 8 May 2002 18:06:18 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 8 May 2002 18:06:18 -0000 Received: (qmail 27438 invoked by uid 97); 8 May 2002 18:06:20 -0000 Delivered-To: qmlist-jakarta-archive-lucene-dev@jakarta.apache.org Received: (qmail 27388 invoked by uid 97); 8 May 2002 18:06:19 -0000 Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Developers List" Reply-To: "Lucene Developers List" Delivered-To: mailing list lucene-dev@jakarta.apache.org Received: (qmail 27366 invoked by uid 98); 8 May 2002 18:06:18 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <3CD96949.20604@apache.org> Date: Wed, 08 May 2002 14:07:05 -0400 From: "Andrew C. Oliver" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc1) Gecko/20020417 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lucene Developers List Subject: Re: cvs commit: jakarta-lucene/src/java/org/apache/lucene/search DateFilter.java References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Thats fine Jon. I'm not really up to explaining it to you. I'm going to do it via crontab. Once I'm done with it I'll send you the script if you're interested in implementing it for Lucene or Maven to free you up from your task as code formatting security: http://jakarta.apache.org/site/jon.html -- Give you more time to argue. ;-) -Andy Jon Scott Stevens wrote: >on 5/8/02 5:13 AM, "Andrew C. Oliver" wrote: > > > >>I'm going to do it in the crontab. Yes it is technically possible >>otherwise, no I don't care to have a lengthy discussion about it, as I >>think doing it in the crontab is better. *everything* is technically >>possible, its all a matter of costs and risks. >> >>-Andy >> >> > >Andy, now you are just being silly. > >Think about it: > >#1. You change a file. >#2. You cvs commit it. >#3. Diff gets sent to the server. >#4. Server then checks out a copy of the file and changes it and checks it >in again. >#5. File on local disk is different than file on server. >#6. User who did the commit does a cvs update. > >At #4, you will get two commit messages for every commmit. > >At #6, when the user does a cvs update, they are going to get a bunch of >conflicts because the lines changed from the version on the server to the >version on the client. > >-jon > > >-- >To unsubscribe, e-mail: >For additional commands, e-mail: > > > > -- To unsubscribe, e-mail: For additional commands, e-mail: