I do B then put the patches in Jira in case someone wants to use them.

=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation 
<http://www.businessesnetwork.com/automation/viewforum.php?f=93>
Specialtymarket.com <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat  Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>


Chris Snow sent the following on 5/15/2010 2:30 AM:
> If there is one patch per entity, only one or two patches waiting to be
> committed at any one time, one month to commit each patch, that's alot of
> patience (100+ months)!
> 
> It sounds like my options are:
> 
> A) not bother doing anything
> B) setup my own local svn that is a mirror of the apache svn server
> 
>> Yeah, be patient. I had patches sitting in Jira for years before they were
>> committed.
>>
>> -Adrian
>>
>>
>> --- On Sat, 5/15/10, Scott Gray <[email protected]> wrote:
>>
>>> From: Scott Gray <[email protected]>
>>> Subject: Re: Making the dev process work...
>>> To: [email protected]
>>> Date: Saturday, May 15, 2010, 1:42 AM
>>> No it's not possible (well
>>> technically it is but it's very unlikely to happen).
>>>
>>> Just be patient and they'll get committed.
>>>
>>> Regards
>>> Scott
>>>
>>> HotWax Media
>>> http://www.hotwaxmedia.com
>>>
>>> On 15/05/2010, at 6:56 PM, Chris Snow wrote:
>>>
>>>> A while back, I had a small improvement committed to
>>> provide field tooltip
>>>> help.
>>>>
>>>> I now have the time consuming process of extracting
>>> the tooltip help text
>>>> from the manager references and putting it into the
>>> xml property files.
>>>> The problem is that I have to rely on commiters to
>>> take my patches, review
>>>> and commit them.  Erwan is kindly reviewing my
>>> patch for the ProductStore
>>>> and will hopefully commit it at some stage. 
>>> However, committers have
>>>> other priorities and getting the huge amount of
>>> patches that I will be
>>>> providing to be committed is going to be very
>>> timeconsuming!  Contributing
>>>> to the problem is that I don't want to spend more that
>>> half a day on a
>>>> single patch - I can't aford to lose time on writing
>>> patches that may not
>>>> get committed.
>>>>
>>>> Is it possible to give fine grained svn access, I.e.
>>> just to the property
>>>> files that contain the field descriptions?
>>>>
>>>> Any other ideas?
>>>>
>>>> Many thanks,
>>>>
>>>>
>>>> Chris
>>>>
>>>
>>
>>
>>
> 
> 


Reply via email to