Re: [PATCH v5 0/7] Add series support

2016-10-13 Thread Stephen Finucane
On 2016-10-12 23:41, Daniel Axtens wrote: Daniel Axtens writes: - "untitled series #420" is certainly better than having every series named "untitled series", but I still think it's worse than "series starting with '[1/10] add foo to bar'" Should be trivial enough change. I wonder if we s

Re: [PATCH v5 0/7] Add series support

2016-10-12 Thread Daniel Axtens
Daniel Axtens writes: >>> - "untitled series #420" is certainly better than having every series >>> named >>> "untitled series", but I still think it's worse than "series starting >>> with >>> '[1/10] add foo to bar'" >> >> Should be trivial enough change. I wonder if we should save this into

Re: [PATCH v5 0/7] Add series support

2016-10-12 Thread Daniel Axtens
>> - "untitled series #420" is certainly better than having every series >> named >> "untitled series", but I still think it's worse than "series starting >> with >> '[1/10] add foo to bar'" > > Should be trivial enough change. I wonder if we should save this into > the db on calculate it on th

Re: [PATCH v5 0/7] Add series support

2016-10-11 Thread Stephen Finucane
On 2016-10-11 09:14, Stephen Finucane wrote: On 2016-10-11 00:51, Russell Currey wrote: [snip] - no easy way to download a mbox file of all patches in a series, which would be very useful Yup, this is an easy follow up. - no series in the patch API at all.  This could probably be impleme

Re: [PATCH v5 0/7] Add series support

2016-10-11 Thread Stephen Finucane
On 2016-10-11 00:51, Russell Currey wrote: On Sun, 2016-10-09 at 23:25 +0100, Stephen Finucane wrote: Add support for series. Series are groups of patches sent as one bundle. For example: [PATCH 0/3] A cover letter   [PATCH 1/3] The first patch   [PATCH 2/3] The second patch   [

Re: [PATCH v5 0/7] Add series support

2016-10-10 Thread Daniel Axtens
> I don't think all of this stuff would need to be included in the initial > implementation, and I think one of us would be able to work on it.  Are you > aware of anything here that would be backwards incompatible that might need to > go in now?  The only thing I can think of would be the series n

Re: [PATCH v5 0/7] Add series support

2016-10-10 Thread Andrew Donnellan
On 11/10/16 11:51, Russell Currey wrote: - no series in the patch API at all. This could probably be implemented a few different ways, but having no series at all is limiting I'm looking at this currently. -- Andrew Donnellan OzLabs, ADL Canberra andrew.donnel...@au1.ibm.com IBM

Re: [PATCH v5 0/7] Add series support

2016-10-10 Thread Russell Currey
On Sun, 2016-10-09 at 23:25 +0100, Stephen Finucane wrote: > Add support for series. Series are groups of patches sent as one > bundle. For example: > > [PATCH 0/3] A cover letter >   [PATCH 1/3] The first patch >   [PATCH 2/3] The second patch >   [PATCH 3/3] The third patch > >

Re: [PATCH v5 0/7] Add series support

2016-10-10 Thread Stephen Finucane
On 2016-10-10 01:41, Andrew Donnellan wrote: On 10/10/16 09:25, Stephen Finucane wrote: Add support for series. Series are groups of patches sent as one bundle. For example: [PATCH 0/3] A cover letter [PATCH 1/3] The first patch [PATCH 2/3] The second patch [PATCH 3/3] The

Re: [PATCH v5 0/7] Add series support

2016-10-09 Thread Andrew Donnellan
On 10/10/16 09:25, Stephen Finucane wrote: Add support for series. Series are groups of patches sent as one bundle. For example: [PATCH 0/3] A cover letter [PATCH 1/3] The first patch [PATCH 2/3] The second patch [PATCH 3/3] The third patch Looks like patch 4 didn't make

[PATCH v5 0/7] Add series support

2016-10-09 Thread Stephen Finucane
Add support for series. Series are groups of patches sent as one bundle. For example: [PATCH 0/3] A cover letter [PATCH 1/3] The first patch [PATCH 2/3] The second patch [PATCH 3/3] The third patch The following features are currently provided: Parsing === * Creation o