On 2016-3-11 08:41 , David Evans wrote:
On 3/10/16 12:29 PM, Ryan Schmidt wrote:
On Mar 10, 2016, at 12:48 AM, Mojca Miklavec wrote:
On 10 March 2016 at 05:48, Ryan Schmidt wrote:
Obviously nobody is going to commit something they believe is broken, but it
does sometimes end up being the c
On 3/10/16 12:29 PM, Ryan Schmidt wrote:
>
> On Mar 10, 2016, at 12:48 AM, Mojca Miklavec wrote:
>
>> On 10 March 2016 at 05:48, Ryan Schmidt wrote:
>>>
>>> Obviously nobody is going to commit something they believe is broken, but
>>> it does sometimes end up being the case for some subset of us
On Mar 10, 2016, at 12:48 AM, Mojca Miklavec wrote:
> On 10 March 2016 at 05:48, Ryan Schmidt wrote:
>>
>> Obviously nobody is going to commit something they believe is broken, but it
>> does sometimes end up being the case for some subset of users. When it does,
>> and we learn that it has ha
On Thu, Mar 10, 2016 at 1:48 AM, Mojca Miklavec wrote:
>
> When I was testing wxWidgets, discovered a problem and submitted a
> patch, I noticed what they are doing now (which is some light years
> more advanced compared to what they did a few years back when most of
> the tickets were stuck igno
> Am 10.03.2016 um 07:48 schrieb Mojca Miklavec :
>
> The point is that this is all done *in advance* and avoids a lot of
> problems. I would love to see something similar being done for patches
> submitted to our Trac. Of course they would have to be submitted in a
> different way and I'm aware
(Was: Why do so many builds fail? @ macports-users)
On 10 March 2016 at 05:48, Ryan Schmidt wrote:
>
> Obviously nobody is going to commit something they believe is broken, but it
> does sometimes end up being the case for some subset of users. When it does,
> and we learn that it has happened,
