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.
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 | 4 ++--
patchwork/views/patch.py|
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
It is now possible to parse and store series, so do just that.
The parsing at the moment is based on both RFC822 headers and
subject lines.
Signed-off-by: Stephen Finucane
---
v3:
- Rework how nested series are handled once again
- Don't search for references when