On 02/12/2014 02:36 PM, Petr Viktorin wrote:
On 02/10/2014 01:59 PM, Martin Kosek wrote:
On 02/10/2014 01:55 PM, Petr Viktorin wrote:
[...]
I'll use some time this week to write a better patch-pushing helper
that'll
incorporate this.
(For the record, now we usually use
https://github.com/mkose
On 02/10/2014 01:59 PM, Martin Kosek wrote:
On 02/10/2014 01:55 PM, Petr Viktorin wrote:
[...]
I'll use some time this week to write a better patch-pushing helper that'll
incorporate this.
(For the record, now we usually use
https://github.com/mkosek/ipa-tools/blob/master/pushpatch.py)
That m
On Mon, Feb 10, 2014 at 01:59:27PM +0100, Martin Kosek wrote:
> On 02/10/2014 01:55 PM, Petr Viktorin wrote:
> > On 02/10/2014 01:32 PM, Martin Kosek wrote:
> >> Hello,
> >>
> >> I would like to follow up on a core devel team discussion we had last
> >> week. We
> >> found out, that it would be be
On 02/10/2014 01:55 PM, Petr Viktorin wrote:
> On 02/10/2014 01:32 PM, Martin Kosek wrote:
>> Hello,
>>
>> I would like to follow up on a core devel team discussion we had last week.
>> We
>> found out, that it would be beneficial to see a reviewer of the patches that
>> land in our git.
>>
>> Thi
On 02/10/2014 01:32 PM, Martin Kosek wrote:
Hello,
I would like to follow up on a core devel team discussion we had last week. We
found out, that it would be beneficial to see a reviewer of the patches that
land in our git.
This will serve both as a nice way to both generate statistics who is d
Hello,
I would like to follow up on a core devel team discussion we had last week. We
found out, that it would be beneficial to see a reviewer of the patches that
land in our git.
This will serve both as a nice way to both generate statistics who is devoted
to both writing new code, but also to r
