Ouch! Wanted to do it but got

 $ svn up
 svn: REPORT of '/repos/asf/!svn/vcc/default': Could not read chunk
size: Secure connection truncated (https://svn.apache.org)

instead. Maybe try later?
Me now -> bed.

cheers
--
Torsten

On Mon, May 18, 2009 at 22:29, Henri Yandell <flame...@gmail.com> wrote:
> Sounds good. If no one does it, I'll make the SVN karma change tonight
> to add you to the sandbox. If you have karma to do that, feel free.
>
> General approach for proper is to either work on a dev proposal in
> sandbox if you have a lot, or to work on issues in JIRA via patches.
>
> Hen
>
> On Mon, May 18, 2009 at 9:37 AM, Jim Jagielski <j...@jagunet.com> wrote:
>> eg: for cli, I find the default help/usage text much too limiting;
>> it would be nice to be able to have that completely under user control
>> with some sort of templating interface. It would also be cool if
>> that could also drive the parser being used (by defining usage
>> formating string, the matching parser is chosen) or even get away
>> from a "selection" of parsers and just have 1 super parser. Also '-Xxx1024m'
>> should really be added in.
>>
>> For dbcp, it's basically to help 1.3
>>
>> On May 18, 2009, at 12:08 PM, Henri Yandell wrote:
>>
>>> What kind of work are we talking about?
>>>
>>> ie) What's the sandbox karma for - we're nosy and like to hear about ideas
>>> :)
>>>
>>> For CLI/DBCP - if it's a lot of work then that's a good place to work
>>> on things in the sandbox.
>>>
>>> If rather it's some bugfixes, then best is to attach them as patches
>>> to JIRA issues. I generally shepherd CLI currently and Phil generally
>>> shepherds DBCP - though any of the committers can apply but it gives
>>> you names to hassle if there is no response.
>>>
>>> Hen
>>>
>>> On Mon, May 18, 2009 at 6:29 AM, Jim Jagielski <j...@apache.org> wrote:
>>>>
>>>> If possible, I'd like karma for commons-sandbox. Also, I will
>>>> doing some work on cli and dbcp (to start) and if the PMC would
>>>> like to give me prelim-karma for that as well, that would be
>>>> appreciated :)
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to