> "Yann" == Yann E MORIN writes:
> Jeremy, All,
> On 2014-06-03 22:15 +0800, Jeremy Kerr spake thusly:
>> > I've just rolled out the initial code to patchwork.ozlabs.org. The tag
>> > counts are all at zero to start with; I've triggered a re-parse of all
>> > of the existing comments, so
Hi Jeremy,
On Wed, Jun 11, 2014 at 2:00 AM, Jeremy Kerr wrote:
> Hi Yann,
>
>> How and when are the tags parsed?
>
> They should be parsed when the original patch is received, and when any
> follow-ups are appended to the patch. However:
>
>> I noticed that (in the Buildroot patchwork [0]) some t
On Wed, 2014-06-11 at 17:18 +1000, Jeremy Kerr wrote:
> Hi Thomas,
>
> > Another thing that is missing IMO is a way of sorting the patches by
> > the number of A/R/T tags. Probably not needed to be able to sort them
> > for each individual value, but being able to sort them by the sum of
> > A+R+T
Dear Jeremy Kerr,
On Wed, 11 Jun 2014 17:18:19 +1000, Jeremy Kerr wrote:
> > Another thing that is missing IMO is a way of sorting the patches by
> > the number of A/R/T tags. Probably not needed to be able to sort them
> > for each individual value, but being able to sort them by the sum of
> >
Hi Thomas,
> Another thing that is missing IMO is a way of sorting the patches by
> the number of A/R/T tags. Probably not needed to be able to sort them
> for each individual value, but being able to sort them by the sum of
> A+R+T would be useful so that maintainers can spot immediately which
>
Dear Jeremy Kerr,
On Wed, 11 Jun 2014 10:00:54 +1000, Jeremy Kerr wrote:
> They should be parsed when the original patch is received, and when any
> follow-ups are appended to the patch. However:
>
> > I noticed that (in the Buildroot patchwork [0]) some tags were not
> > accounted for:
> >
Hi Yann,
> How and when are the tags parsed?
They should be parsed when the original patch is received, and when any
follow-ups are appended to the patch. However:
> I noticed that (in the Buildroot patchwork [0]) some tags were not
> accounted for:
> http://patchwork.ozlabs.org/patch/354654
Jeremy, All,
On 2014-06-03 22:11 +0800, Jeremy Kerr spake thusly:
> I've just rolled out the initial code to patchwork.ozlabs.org. The tag
> counts are all at zero to start with;
How and when are the tags parsed?
I noticed that (in the Buildroot patchwork [0]) some tags were not
accounted for:
Jeremy, All,
On 2014-06-03 22:15 +0800, Jeremy Kerr spake thusly:
> > I've just rolled out the initial code to patchwork.ozlabs.org. The tag
> > counts are all at zero to start with; I've triggered a re-parse of all
> > of the existing comments, so the counts should reflect reality when that
> > p
Hi all,
> I've just rolled out the initial code to patchwork.ozlabs.org. The tag
> counts are all at zero to start with; I've triggered a re-parse of all
> of the existing comments, so the counts should reflect reality when that
> process finishes.
On second thoughts, I've disabled the display of
Hi Yann,
>> How's this look?
>>
>> http://ozlabs.org/~jk/tmp/patchwork-ART.png
>
> Just a little reminder on this...
>
> When are you planning on deploying that?
> Will it also show up in the output of pwclient?
I've just rolled out the initial code to patchwork.ozlabs.org. The tag
counts are
Jeremy, All,
On 2014-05-07 16:42 +0800, Jeremy Kerr spake thusly:
> > We would like to suggest that the web GUI and the pwclient CLI both
> > display such tags besides each patch, a bit like (hypotetical output of
> > pwclient):
>
> OK, I have some progress on this one; but wanted to make sure wh
On Wed, May 7, 2014 at 1:42 AM, Jeremy Kerr wrote:
> Hi all,
>
>> We would like to suggest that the web GUI and the pwclient CLI both
>> display such tags besides each patch, a bit like (hypotetical output of
>> pwclient):
>
> OK, I have some progress on this one; but wanted to make sure what I'm
Jeremy, All,
On 2014-05-07 16:42 +0800, Jeremy Kerr spake thusly:
> > We would like to suggest that the web GUI and the pwclient CLI both
> > display such tags besides each patch, a bit like (hypotetical output of
> > pwclient):
>
> OK, I have some progress on this one; but wanted to make sure wh
Hi,
On 2014-05-07 16:42:51 +0800, Jeremy Kerr wrote:
>
> > We would like to suggest that the web GUI and the pwclient CLI both
> > display such tags besides each patch, a bit like (hypotetical output of
> > pwclient):
>
> OK, I have some progress on this one; but wanted to make sure what I'm
> d
> How's this look?
>
> http://ozlabs.org/~jk/tmp/patchwork-ART.png
Looks great, I like it!
> Also, are you wanting to filter by the presence of these tags? Just
> non-zero? How about sorting?
I would love sorting per flag. However, if filtering non-zero is much
less work, I can make a workfl
Dear Jeremy Kerr,
On Wed, 07 May 2014 16:42:51 +0800, Jeremy Kerr wrote:
> OK, I have some progress on this one; but wanted to make sure what I'm
> doing is in the direction that'd be generally useful for you.
>
> How's this look?
>
> http://ozlabs.org/~jk/tmp/patchwork-ART.png
>
> - there a
Hi all,
> We would like to suggest that the web GUI and the pwclient CLI both
> display such tags besides each patch, a bit like (hypotetical output of
> pwclient):
OK, I have some progress on this one; but wanted to make sure what I'm
doing is in the direction that'd be generally useful for you.
Jeremy, All,
On 2013-11-11 22:54 +0100, Yann E. MORIN spake thusly:
[--SNIP--]
> We would like to suggest that the web GUI and the pwclient CLI both
> display such tags besides each patch, a bit like (hypotetical output of
> pwclient):
>
> ID Tags State Subject
> 123456 ART New
On Tue, Dec 03, 2013 at 11:49:27PM +0100, Yann E. MORIN wrote:
> Jeremy, All,
>
> On 2013-11-12 08:37 +0800, Jeremy Kerr spake thusly:
> > > We would like to suggest that the web GUI and the pwclient CLI both
> > > display such tags besides each patch, a bit like (hypotetical output of
> > > pwcli
Jeremy, All,
On 2013-11-12 08:37 +0800, Jeremy Kerr spake thusly:
> > We would like to suggest that the web GUI and the pwclient CLI both
> > display such tags besides each patch, a bit like (hypotetical output of
> > pwclient):
> >
> > ID Tags State Subject
> > 123456 ART New
Arnout, All,
On 2013-11-12 09:10 +0100, Arnout Vandecappelle spake thusly:
> I think the ART flags in the patch list should never be used blindly
> anyway. Instead, it's an indicator of which patches are interesting to look
> at in more detail. Right?
That's the way I would use it, yes:
- as a
On Wed, 2013-11-20 at 09:43 +0100, Wolfram Sang wrote:
> > I think the ART flags in the patch list should never be used
> > blindly anyway. Instead, it's an indicator of which patches are
> > interesting to look at in more detail. Right?
>
> +1
+1
___
> I think the ART flags in the patch list should never be used
> blindly anyway. Instead, it's an indicator of which patches are
> interesting to look at in more detail. Right?
+1
signature.asc
Description: Digital signature
___
Patchwork mailing list
Hi,
On Tue, Nov 12, 2013 at 7:58 AM, Thomas Petazzoni
wrote:
[..]
>> Other projects have different policies for their tagging (some require 3
>> acks, for example), which will introduce a little complexity there too,
>> but that's not insurmountable either.
>
> Another thing that comes to mind is
On 12/11/13 07:58, Thomas Petazzoni wrote:
Dear Jeremy Kerr,
On Tue, 12 Nov 2013 08:37:26 +0800, Jeremy Kerr wrote:
We would like to suggest that the web GUI and the pwclient CLI both
display such tags besides each patch, a bit like (hypotetical output of
pwclient):
ID Tags State
Dear Jeremy Kerr,
On Tue, 12 Nov 2013 08:37:26 +0800, Jeremy Kerr wrote:
> > We would like to suggest that the web GUI and the pwclient CLI both
> > display such tags besides each patch, a bit like (hypotetical output of
> > pwclient):
> >
> > ID Tags State Subject
> > 123456 A
Hi Yann,
> We would like to suggest that the web GUI and the pwclient CLI both
> display such tags besides each patch, a bit like (hypotetical output of
> pwclient):
>
> ID Tags State Subject
> 123456 ART New Wonderfull patch to apply quickly
I've been looking to imple
Hello All!
In the Buildroot community, we make heavy use of patchwork to track the
patches that we still have pending. The maintainer (Peter, CCed) almost
exclusively use pwclient to get that list of patches to apply.
Since we also use the Linux-like tags Acked-by, Reviewed-by and
Tested-by, this
29 matches
Mail list logo
