Re: [PATCH 2/2] xmlrpc: Treat negative max_count as meaning "return last N results"

2016-03-31 Thread Finucane, Stephen
On 31 Mar 15:08, Damien Lespiau wrote: > On Fri, Feb 05, 2016 at 05:21:20PM +, Stephen Finucane wrote: > > @@ -602,6 +607,8 @@ def patch_list(filt=None): > > > > if max_count > 0: > > return list(map(patch_to_dict, patches[:max_count])) > > +elif max_count < 0:

Re: [PATCH 2/2] xmlrpc: Treat negative max_count as meaning "return last N results"

2016-03-31 Thread Damien Lespiau
On Fri, Feb 05, 2016 at 05:21:20PM +, Stephen Finucane wrote: > @@ -602,6 +607,8 @@ def patch_list(filt=None): > > if max_count > 0: > return list(map(patch_to_dict, patches[:max_count])) > +elif max_count < 0: > +return list(map(patch_to_dict,

Re: [PATCH 2/2] xmlrpc: Treat negative max_count as meaning "return last N results"

2016-02-08 Thread Finucane, Stephen
On 05 Feb 17:21, Stephen Finucane wrote: > From: Adam Jackson > > This is most useful when listing patches, as it lets you get the most > recent results instead of the oldest. > > v2: Resolve "Negative indexing is not supported." issue and include > unit tests to ensure

[PATCH 2/2] xmlrpc: Treat negative max_count as meaning "return last N results"

2016-02-05 Thread Stephen Finucane
From: Adam Jackson This is most useful when listing patches, as it lets you get the most recent results instead of the oldest. v2: Resolve "Negative indexing is not supported." issue and include unit tests to ensure this doesn't regress. Bump API version to 1.2