[PATCH 10/10] models: Enable "auto-completion" of series patches

Users can send a new revision of a single patch from a series. When this happens there is no immediate context: one must grok the previous series to understand that this new patch is in fact a minor change to an existing series and not a new, standalone hanges. This is particularly impactful for

[PATCH 08/10] templates: Integrate series view into patches

Patches for related series are listed on the patch page - this provides a way to quickly grok a given patches location in a series hierarchy. Signed-off-by: Stephen Finucane --- htdocs/css/style.css |6 +++

[PATCH 02/10] models: Add 'Series' model and related models

Add a series model. This model is intentionally very minimal to allow as much dynaminism as possible. It is expected that patches will be migrated between series as new data is provided. Signed-off-by: Stephen Finucane --- v2: - Rename 'SeriesGroup' to 'Series' -

[PATCH 06/10] templates: Generate and use a "handle"

In the absence of a name, the email is currently used. Some emails are long and rather unreadable. The likelihood of someone's localpart (i.e. the bit before the '@') conflicting with that of someone else on the same patchwork instance and project is very low, so form a "handle" from just this.

[PATCH 01/10] models: Convert functions to properties

A number of models contain functions that are, semantically speaking, actually properties. Mark them as such. Signed-off-by: Stephen Finucane --- patchwork/models.py | 15 ++- patchwork/views/__init__.py |2 +- patchwork/views/patch.py|

[PATCH 04/10] parsemail: Handle 'xxx (v2)' style messages

Some emails are received in the above format. Might as well support them. Signed-off-by: Stephen Finucane --- patchwork/bin/parsemail.py | 11 --- 1 files changed, 8 insertions(+), 3 deletions(-) diff --git a/patchwork/bin/parsemail.py

[PATCH 00/10] Add series support

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

[PATCH 05/10] parsemail: Handle series sent "in-reply-to"

Take a series, "v2", sent as a reply to another, "v1", like so: [PATCH 0/3] A cover letter [PATCH 1/3] The first patch ... [PATCH v2 0/3] A cover letter [PATCH v2 1/3] The first patch ... The current behavior for traversing references is oldest first. For