[PATCH 2/2] Patchwork v2.1.0-rc1

Signed-off-by: Daniel Axtens --- patchwork/__init__.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/patchwork/__init__.py b/patchwork/__init__.py index 98e9b21d066f..d145a4dbce67 100644 --- a/patchwork/__init__.py +++ b/patchwork/__init__.py @@ -19,7 +19,7 @@ from patchw

[PATCH 1/2] docs: Prepare for 2.1.0-rc1

Explain why we want an extra special ozlabs edition. (I can't find any good fabrics starting with E and I also want to emphasise that this is a special case.) Signed-off-by: Daniel Axtens --- docs/conf.py | 4 ++-- docs/index.rst

[PATCH 0/2] Patchwork 2.1.0-rc1: Extra Special OzLabs Edition

TL;DR: I want to spin a new version of patchwork for OzLabs so they can do the migration that speeds up patch listing. I've pushed it to https://github.com/daxtens/patchwork as I'm not sufficiently confident in my release-fu to push it to the main repo just yet. Let me know if it looks good. From

[PATCH v2] Include all email headers in mboxes

From: Veronika Kabatova Solves issue #165 (Exported mboxes should include In-Reply-To, References, etc headers). Instead of including only a few chosen ones, all received headers are added to mboxes. Signed-off-by: Veronika Kabatova --- patchwork/views/utils.py | 8 ++-- 1 file changed, 2

Re: [PATCH] Include all email headers in mboxes

>> > That said, using a dict for this is in general not quite right, since >> > many header lines are valid multiple times, e.g. "Received:", but I'm >> > not sure they're even all stored. >> >> Right, you and Veronika have convinced me. Clearly as a developer of >> patchwork my view is a bit skew

Re: [PATCH] Include all email headers in mboxes

- Original Message - > From: "Daniel Axtens" > To: "Johannes Berg" , vkaba...@redhat.com, > patchwork@lists.ozlabs.org > Sent: Thursday, April 5, 2018 3:47:03 PM > Subject: Re: [PATCH] Include all email headers in mboxes > > Johannes Berg writes: > > > On Thu, 2018-04-05 at 19:58 +100

Re: [PATCH] Include all email headers in mboxes

Johannes Berg writes: > On Thu, 2018-04-05 at 19:58 +1000, Daniel Axtens wrote: >> vkaba...@redhat.com writes: >> >> > From: Veronika Kabatova >> > >> > Solves issue #165 (Exported mboxes should include In-Reply-To, >> > References, etc headers). Instead of including only a few chosen ones, >>

Re: [PATCH docs] Fix incorrect autodelegation documentation

vkaba...@redhat.com writes: > From: Veronika Kabatova > > The docs suggested to account for git prefixes (a/, b/) using eg. > ?/patchwork/views/*. My rules didn't work so I tried bare path > (patchwork/views/*) instead. Looking at the code, the prefix really is > striped away (filename = '/'.join

Re: [PATCH] Include all email headers in mboxes

On Thu, 2018-04-05 at 19:58 +1000, Daniel Axtens wrote: > vkaba...@redhat.com writes: > > > From: Veronika Kabatova > > > > Solves issue #165 (Exported mboxes should include In-Reply-To, > > References, etc headers). Instead of including only a few chosen ones, > > all received headers are added

Re: [PATCH] Include all email headers in mboxes

- Original Message - > From: "Daniel Axtens" > To: vkaba...@redhat.com, patchwork@lists.ozlabs.org > Sent: Thursday, April 5, 2018 11:58:15 AM > Subject: Re: [PATCH] Include all email headers in mboxes > > vkaba...@redhat.com writes: > > > From: Veronika Kabatova > > > > Solves issue #

Re: [PATCH] Include all email headers in mboxes

vkaba...@redhat.com writes: > From: Veronika Kabatova > > Solves issue #165 (Exported mboxes should include In-Reply-To, > References, etc headers). Instead of including only a few chosen ones, > all received headers are added to mboxes. Thanks for the patch. I'm a little worried that this will

Re: [PATCH] docker: set timezone to Australia/Canberra

Applied, thanks Stephen. Daniel Axtens writes: > The tzinfo package isn't installed in docker, which makes the > default timezone UTC. This is unfortunate: the Django TZ in > settings/base.py is Australia/Canberra, and having a non-UTC > TZ is good for exposing faulty assumptions about what is a

Re: [PATCH v2 1/2] api: EventList: change select_related() to prefetch_related()

These are conceptually compatible with Stephen's ongoing refactoring, whether or not we go ahead with that in the end, this at least doesn't close it off. Applied. Regards, Daniel Daniel Axtens writes: > select_related() creates a single giant query that JOINs the required > tables together in

Re: [PATCH] docs: Update reference to kernel documentation

Hi Ali, Thanks for your contributions to Patchwork! I have applied them and will push to master shortly. Regards, Daniel > The referenced url was moved to Documentation/process. > > Signed-off-by: Ali Alnubani > --- > docs/usage/overview.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletio