On Sunday, September 25, 2011 15:55:07 Wolfgang Denk wrote:
> Using gerrit? Hm... All my work in this context is e-mail based, and
> I think many others work in a similar way. Web-based tools may be
> more "modern", but I have to admit that I am not convinced that they
> are any more helpful or e
Hi Wolfgang,
On Monday, September 26, 2011, Wolfgang Denk wrote:
> Dear Graeme Russ,
>
> In message <4e7c63a0.5050...@gmail.com> you wrote:
>>
>> > That would be easy to do...
>>
>> Maybe that's what we do - Once a patch reaches maturity (a revision with
an
>> Ack and maybe a Tested-by) any maint
Dear Graeme Russ,
In message <4e7c63a0.5050...@gmail.com> you wrote:
>
> > Just add them to my ToDo list by assigning them to me...
>
> Done - They are still 'New' (didn't know if you wanted that changed)
Thanks. "New" is ok - it's what I expect for patche that have not
been applied anywhere y
Am 23/09/2011 12:23, schrieb Wolfgang Denk:
> Dear Stefano Babic,
>
Hi Wolfgang,
> In message <4e7c59b4.50...@denx.de> you wrote:
>>
>
> I have asked before if we could get patchwork to acto on X- mail
> headers - then it would be sufficient to add a line
>
> X-PATCHWORK-STATUS: Changes
On 23/09/11 20:18, Wolfgang Denk wrote:
> Dear Graeme Russ,
>
> In message <4e7c4f80.6070...@gmail.com> you wrote:
>>
>> Well my two console patches are ready for the next merge window - I notice
>> you have not claimed them, so I'll ping you when it opens
>
> Just add them to my ToDo list by ass
Dear Stefano Babic,
In message <4e7c59b4.50...@denx.de> you wrote:
>
> Maybe we have to start updating patchwork directly after sending our
> answers to the ML to maintain the tool synchron. I was used to update
I think the main problem is if this is indeed two separate steps. As
soon as it becom
Dear Graeme Russ,
In message <4e7c4f80.6070...@gmail.com> you wrote:
>
> Well my two console patches are ready for the next merge window - I notice
> you have not claimed them, so I'll ping you when it opens
Just add them to my ToDo list by assigning them to me...
> > In the result, a huge patc
Hi Stefano,
On 23/09/11 20:04, Stefano Babic wrote:
> On 09/23/2011 11:21 AM, Graeme Russ wrote:
> Maybe we have to start updating patchwork directly after sending our
> answers to the ML to maintain the tool synchron. I was used to update
> patchwork after answering several messages to the ML an
On 09/23/2011 11:21 AM, Graeme Russ wrote:
>>> Just wondering how we should be tracking said patches - Do you want us to
>>> ping you when the Merge Window opens, or do you have them nicely piled up
>>> in Patchwork ready to apply?
>>
>> Also in theory, most of the patches should go through the re
Hi Wolfgang,
On 23/09/11 17:25, Wolfgang Denk wrote:
> Dear Graeme Russ,
>
> In message
> you
> wrote:
>>
>> With the next release pending and the next Merge Window about to open, I
>> thought I might take the opportunity to ask a question that's been on my
>> mind...What is the 'procedure' (f
Dear Graeme Russ,
In message
you wrote:
>
> With the next release pending and the next Merge Window about to open, I
> thought I might take the opportunity to ask a question that's been on my
> mind...What is the 'procedure' (for want of a better word) you use for
> patches applied during the m
Hi Wolfgang,
With the next release pending and the next Merge Window about to open, I
thought I might take the opportunity to ask a question that's been on my
mind...What is the 'procedure' (for want of a better word) you use for
patches applied during the merge window?
Now I know maintainers typ
12 matches
Mail list logo
