Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of eljotpl@gmail.com designates
 64.233.166.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=WrAq/1cjQMyzNKju/Hf9S4S5CgSyAvlzE76wS/RUOWplXsDSzMF1v+u2YlvOrtbBRoswwDHUAGFbrGO1VOM6swwvaPtGiszYCYw3LpwKGwyLClTMeHvfaWystYadPs5h+dVmMKu87n8MLSsqSomfbqO3zuHNh32JnCe+QyCoXVA=
Message-ID: <1b5bfeb50607062354j3339c0esc2875e82c9702ff3@mail.gmail.com>
Date: Fri, 7 Jul 2006 08:54:51 +0200
From: "Jacek Laskowski" <jacek@laskowski.net.pl>
Reply-To: jacek@laskowski.net.pl
Sender: eljotpl@gmail.com
To: dev@geronimo.apache.org
Subject: Re: [RTC] Vote on GERONIMO-2161 - restart 1
In-Reply-To: <B6DB7B43-DB5D-4A43-85CC-1CDEFF341F3C@planet57.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <44AD16CE.1020705@hogstrom.org>
	 <153B723F-DE2F-49A4-A173-03FE8214BF0A@planet57.com>
	 <44AD7BDB.8090402@apache.org>
	 <0ABA4BBF-D335-47D5-BAD0-7AA4007B5F20@planet57.com>
	 <CE1AD76A-BF2F-4C6C-A118-2E51B4B82808@yahoo.com>
	 <2DCB9D47-2588-4A8B-BAE9-13BB1464BA49@planet57.com>
	 <44ADA2BB.8000401@apache.org>
	 <B6DB7B43-DB5D-4A43-85CC-1CDEFF341F3C@planet57.com>

On 7/7/06, Jason Dillon <jason@planet57.com> wrote:
> This is applied.
>
> :-)
>
> Took longer than expected because I happened to switch to a terminal
> that was set to use JDK 1.5 and I did not realize it... until a few
> hours later after I was pulling my hair out wondering why the patch
> god hates me so much.

It's because it needs a solution as I think you won't be alone in your
pain of applying patches/changes that are incompatible with the unix
patch command.

I think it would be much better if the person who makes a change is
not the one who commits it to trunk, but the last PMCer who voted for
it. And a branch the change is built from is established. The solution
has such a good effect that the person who works on changes don't have
to worry about the commit date until it's rejected when (s)he or
anyone else will fix it and a vote starts over (with 24-hour time
period). Another good effect is that knowing the revisions a change
that's being voted, one can continue his/her work without worrying
about disrupting the vote process as the revisions are still in the
branch. Phew, I do like the idea! ;-)

WDYT?

> --jason

Jacek

-- 
Jacek Laskowski
http://www.laskowski.net.pl