We need steenking patches (Re: Cygwin kill utility...)
Fri Apr 11 11:05:00 GMT 2014
Greetings, Corinna Vinschen!
>> > On Wed, Apr 9, 2014 at 11:50 AM, Warren Young wrote:
>> >> If you think web code repository searching and a public bug tracker are
>> >> primary barriers to contribution, you aren't being honest with yourself.
>> >> They are nice, but not necessary.
>> > I am honest with myself. I, as everyone have limited time.
>> Seems like the limit on your time is very laxed.
>> For the time you wrote all the posts to this list, I've downloaded whole
>> Cygwin /cvs/src, found the offended string, patched the file, and it took me 2
>> days to rebuild it only because I wasn't familiar with out-of-the tree build
>> system. (Had to read building instructions first, yeah...)
>> Now, I'm a happy owner of a custom cygpath that doesn't annoy me with
>> insignificant warnings.
> Wanna send the patch to cygwin-patches(*)?
I'm not quite happy with it yet. I'll need to dig through that function
another pass to see, if I can completely avoid the code path in question
without harming any hamsters in process.
Besides, when I digged through it, I got an idea of completely new
functionality. That may be the one I want to contribute.
Andrey Repin (firstname.lastname@example.org) 11.04.2014, <15:01>
Sorry for my terrible english...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin