[PATCH 5/5] Add release notes: project patches as mbox

Signed-off-by: Mete Polat --- .../notes/project-patches-mbox-623f8c9d4cf6a952.yaml| 6 ++ 1 file changed, 6 insertions(+) create mode 100644 releasenotes/notes/project-patches-mbox-623f8c9d4cf6a952.yaml diff --git a/releasenotes/notes/project-patches-mbox-623f8c9d4cf6a952.yaml b

[PATCH 1/5] Add option to get all project patches in one mbox

FilenameMixin.filename(self) returns a sanitized filename based on the str representation of the object. In our case str(project) returns the project name. Thus the output file will be .mbox Signed-off-by: Mete Polat --- patch_list_mbox() and project_patches_to_mbox() are not named project_mbox

[PATCH 0/5] Update REST API: Add 'project patches as mbox' field

patchwork.example.com/project//list/ the final project.mbox only includes patches. Careful naming has been made in case the api should support export of a whole project in the future as well. Mete Polat (5): Add option to get all project patches in one mbox Add url to get all project patches in one mbox Add

[PATCH 2/5] Add url to get all project patches in one mbox

New url: project//list/mbox/ Signed-off-by: Mete Polat --- 'patch-list-mbox' is not named 'project-mbox' in order to prevent confusion. While a project also consists of cover letters, those are not intended to be included. patchwork/urls.py | 2 ++ 1 file changed, 2 inserti

[PATCH 3/5] Add api endpoint for project patches as mbox

Introduces a new field in the project endpoint called 'patches_mbox'. Signed-off-by: Mete Polat --- Again 'patches_mbox' and not 'mbox' in order to prevent confusion. patchwork/api/project.py | 11 +-- patchwork/models.py | 3 +++ 2 files changed,

[PATCH v2 1/5] Add option to get all project patches in one mbox

FilenameMixin.filename(self) returns a sanitized filename based on the str representation of the object. In our case str(project) returns the project name. Thus the output file will be .mbox Signed-off-by: Mete Polat --- patch_list_mbox() and project_patches_to_mbox() are not named project_mbox

[PATCH v2 0/5] Update REST API: Add 'project patches as mbox' field

1.2 Mete Polat (5): Add option to get all project patches in one mbox Add urls to get all project patches in one mbox Add api endpoint for project patches as mbox Update api documentation for v1.2 Add release notes: project patches as mbox docs/api/rest/index.rst

[PATCH v2 2/5] Add urls to get all project patches in one mbox

New api url: api/1.2/ New internal url: project//list/mbox/ Signed-off-by: Mete Polat --- Changes since v1: - Add url pattern for the v1.2 rest api 'patch-list-mbox' is not named 'project-mbox' in order to prevent confusion. While a project also consists of cover letters, th

[PATCH v2 3/5] Add api endpoint for project patches as mbox

Introduces a new field in the project endpoint called 'patches_mbox'. Signed-off-by: Mete Polat --- Again 'patches_mbox' and not 'mbox' in order to prevent confusion. patchwork/api/project.py | 11 +-- patchwork/models.py | 3 +++ 2 files changed,

[PATCH v2 5/5] Add release notes: project patches as mbox

Signed-off-by: Mete Polat --- .../notes/project-patches-mbox-623f8c9d4cf6a952.yaml| 6 ++ 1 file changed, 6 insertions(+) create mode 100644 releasenotes/notes/project-patches-mbox-623f8c9d4cf6a952.yaml diff --git a/releasenotes/notes/project-patches-mbox-623f8c9d4cf6a952.yaml b

Re: [PATCH v2 0/5] Update REST API: Add 'project patches as mbox' field

/ >> New project rest api field: patches_mbox >> >> Like patchwork.example.com/project//list/ the final project.mbox >> only includes patches. Careful naming has been made in case the api should >> support export of a whole project in the future as well. >> >> Ch

Re: [PATCH v2 0/5] Update REST API: Add 'project patches as mbox' field

> On 28-06-2019 17:56, Mete Polat wrote: > >> Patchwork already has the ability to export patches, series, covers and >> bundles >> as an mbox file. This patch extends that ability to projects as well. >> Therefore >> a new url and api field has been introduce

[PATCH 2/3] Update management documentation

Signed-off-by: Mete Polat --- docs/deployment/management.rst | 28 1 file changed, 28 insertions(+) diff --git a/docs/deployment/management.rst b/docs/deployment/management.rst index c50b7b6..70e926c 100644 --- a/docs/deployment/management.rst +++ b/docs/deployment

[PATCH 3/3] Add exportproject cmd release notes

Signed-off-by: Mete Polat --- .../notes/mbox-export-project-cmd-090cb74c68608aa8.yaml | 5 + 1 file changed, 5 insertions(+) create mode 100644 releasenotes/notes/mbox-export-project-cmd-090cb74c68608aa8.yaml diff --git a/releasenotes/notes/mbox-export-project-cmd-090cb74c68608aa8

[PATCH 1/3] Add export project as mbox management command

Introduces a new management command which can export all patches in a project as one mbox file. Export of multiple projects is supported. Additionaly allows to compress the output. Signed-off-by: Mete Polat --- Also supports python2 with the force_bytes() function. .../management/commands

Re: [PATCH 1/3] Add export project as mbox management command

On 15.07.19 17:39, Stephen Finucane wrote: On Mon, 2019-07-15 at 16:50 +0200, Mete Polat wrote: Introduces a new management command which can export all patches in a project as one mbox file. Export of multiple projects is supported. Additionaly allows to compress the output. This looks good

Re: [PATCH 1/3] Add export project as mbox management command

On 19.07.19 15:50, Stephen Finucane wrote: [re-adding the list] On Fri, 2019-07-19 at 14:44 +0200, Lukas Bulwahn wrote: On Mon, Jul 15, 2019 at 5:39 PM Stephen Finucane wrote: On Mon, 2019-07-15 at 16:50 +0200, Mete Polat wrote: [snip] +def add_arguments(self, parser

[PATCH 4/5] Update api documentation for v1.2

Signed-off-by: Mete Polat --- In the index.rst (section 'supported versions') we have to specify since which patchwork version an api version is available. If this patch will be integrated in a patchwork version other than 2.2, the version number has to be updated here. docs/api/rest

[PATCH v2 4/5] Update api documentation for v1.2

Signed-off-by: Mete Polat --- In the index.rst (section 'supported versions') we have to specify since which patchwork version an api version is available. If this patch will be integrated in a patchwork version other than 2.2, the version number has to be updated here. docs/api/rest

Detect commit_ref automatically

Hi Michael, hi all, As you are currently working on adding commit_url_format to Project... How is commit_ref actually set? As far as I have seen the only way setting this field right now is by manually using the API (or git-pw) right? As pointed out in a former mail [1], we are currently working

Re: [PATCH 0/3] Add patch relations

Hi Daniel, > > From: Mete Polat > > > > This patch introduces the ability to view relations between patches by > > creating and updating patch relations via the REST API. Setting > > relations allows users to browse related patches like other revisions of > &

[PATCH 2/5] ui, templates: Combine series and related row

From: Mete Polat Move the series patch list from 'Related' to 'Series' and display the series name, its patches and a detailed link in the same row. This allows to use the 'Related' row for actually showing submission relations instead. Signed-off-by: Mete Po

[PATCH 1/5] ui: Retain table header position on size changes

From: Mete Polat Prevents table header labels from moving up and down when hiding or showing additional information for a patch. Signed-off-by: Mete Polat --- htdocs/css/style.css | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/css/style.css b/htdocs/css/style.css

[PATCH 0/5] Add submission relations

From: Mete Polat This patch introduces the ability to view relations between submissions by creating and updating them via the REST API. Changes since v1: - Allow cover letters to be in relations as well (submission relations) - Move from Django permission to a maintainer based one (and update

[PATCH 3/5] models, templates: Add sumbission relations

From: Mete Polat Introduces the ability to add relations between submissions. Relations are displayed in the details page of a submission under 'Related'. Related submissions located in another projects can be viewed as well. Signed-off-by: Mete Polat --- .../

[PATCH 4/5] docs: Add missing series index schema

From: Mete Polat Signed-off-by: Mete Polat --- This one can probably be cherry-picked immediately. docs/api/schemas/latest/patchwork.yaml | 5 + docs/api/schemas/patchwork.j2 | 5 + docs/api/schemas/v1.0/patchwork.yaml | 5 + docs/api/schemas/v1.1/patchwork.yaml | 5

[PATCH 5/5] REST: Add submission relations

From: Mete Polat View relations or add/update/delete them as a maintainer. Maintainers can only create relations of sumbissions (patches/cover letters) which are part of a project they maintain. New REST API urls: api/relations/ api/relations// Signed-off-by: Mete Polat --- Previously it was

Re: [PATCH 0/5] Add submission relations

Hi Daniel and Lukas, thank you both for your reviews. I will send an updated version shortly. @Daniel Are you OK with the Series row UI chances and the missing hyperlinks in the relations REST API? Best Regards, Mete ___ Patchwork mailing list Patch

[PATCH v3 0/5] Add submission relations

ts) - Drop bulk support I decided to drop the bulk support in favour of an easier implementation, usability and maintainability. - Drop support for manually setting relation id - Group relations from other projects separately - Split up UI changes Mete Polat (5): ui: Retain table header positi

[PATCH v3 3/5] models, templates: Add submission relations

Introduces the ability to add relations between submissions. Relations are displayed in the details page of a submission under 'Related'. Related submissions located in another projects can be viewed as well. Signed-off-by: Mete Polat --- .../migrations/0037_submission_relations

[PATCH v3 2/5] ui, templates: Combine series and related row

Move the series patch list from 'Related' to 'Series' and display the series name, its patches and a detailed link in the same row. This allows to use the 'Related' row for actually showing submission relations instead. Signed-off-by: Mete Po

[PATCH v3 4/5] docs: Add missing series index schema

Signed-off-by: Mete Polat --- docs/api/schemas/latest/patchwork.yaml | 5 + docs/api/schemas/patchwork.j2 | 5 + docs/api/schemas/v1.0/patchwork.yaml | 5 + docs/api/schemas/v1.1/patchwork.yaml | 5 + docs/api/schemas/v1.2/patchwork.yaml | 5 + 5 files changed

[PATCH v3 1/5] ui: Retain table header position on size changes

Prevents table header labels from moving up and down when hiding or showing additional information for a patch. Signed-off-by: Mete Polat --- htdocs/css/style.css | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/css/style.css b/htdocs/css/style.css index fc816d3

[PATCH v3 5/5] REST: Add submission relations

View relations or add/update/delete them as a maintainer. Maintainers can only create relations of submissions (patches/cover letters) which are part of a project they maintain. New REST API urls: api/relations/ api/relations// Signed-off-by: Mete Polat --- Previously it was possible to use the

Re: [PATCH v3 4/5] docs: Add missing series index schema

ine --format=fixes -n 1 > > If you're able to check that and include it in the next revision, that > would be great. As it's a stand-alone fix, I'd also then be happy to > pull it in to master independently. Thank you for the tip! I will add the tag in the next revision.

Re: [PATCH v3 2/5] ui, templates: Combine series and related row

Hi Daniel, On 31.10.19 14:42, Daniel Axtens wrote: > Mete Polat writes: > >> Move the series patch list from 'Related' to 'Series' and display the >> series name, its patches and a detailed link in the same row. This >> allows to use the &

Re: [PATCH v3 5/5] REST: Add submission relations

Hi Daniel, (sorry for the short delay) On 06.11.19 16:12, Daniel Axtens wrote: > Mete Polat writes: > >> View relations or add/update/delete them as a maintainer. Maintainers >> can only create relations of submissions (patches/cover letters) which >> are part of

Re: [PATCH v3 0/5] Add submission relations

Hi Stephen, On 30.11.19 18:19, Stephen Finucane wrote: > On Sun, 2019-10-20 at 20:57 +0200, Mete Polat wrote: >> This patch introduces the ability to view relations between submissions by >> creating and updating them via the REST API. >> >> Changes since v2 (note:

[PATCH 2/4] models, templates: Add submission relations

Introduces the ability to add relations between submissions. Relations are displayed in the details page of a submission under 'Related'. Related submissions located in another projects can be viewed as well. Signed-off-by: Mete Polat --- .../migrations/0038_submission_relations

[PATCH 3/4] docs: Add missing series index schema

Fixes: 7d8e24bc84bd ("docs: Start documenting API using OpenAPI") Signed-off-by: Mete Polat --- docs/api/schemas/latest/patchwork.yaml | 5 + docs/api/schemas/patchwork.j2 | 5 + docs/api/schemas/v1.0/patchwork.yaml | 5 + docs/api/schemas/v1.1/patchwork.

[PATCH 0/4] Add submission relations

ly. They also helped me a lot in finding permission issues. Mete Polat (4): ui, templates: Combine series and related row models, templates: Add submission relations docs: Add missing series index schema REST: Add submission relations docs/api/schemas/latest/patchwo

[PATCH 1/4] ui, templates: Combine series and related row

Move the series patch list from row 'Related' to 'Series'. This allows us to use the 'Related' row for actually showing submission relations instead. Signed-off-by: Mete Polat --- htdocs/css/style.css | 2 +- patchwork/templates/

[PATCH 4/4] REST: Add submission relations

View relations and add/update/delete them as a maintainer. Maintainers can only create relations of submissions (patches/cover letters) which are part of a project they maintain. New REST API urls: api/relations/ api/relations// Co-authored-by: Daniel Axtens Signed-off-by: Mete Polat

Re: [PATCH 4/4] REST: Add submission relations

Hi Stephen, On 27.12.19 18:48, Stephen Finucane wrote: > On Sat, 2019-12-07 at 17:46 +0100, Mete Polat wrote: >> View relations and add/update/delete them as a maintainer. Maintainers >> can only create relations of submissions (patches/cover letters) which >> are part of a

Re: [PATCH 2/4] models, templates: Add submission relations

Hi Stephen, On 27.12.19 19:05, Stephen Finucane wrote: > On Sat, 2019-12-07 at 17:46 +0100, Mete Polat wrote: >> Introduces the ability to add relations between submissions. Relations >> are displayed in the details page of a submission under 'Related'. >> Related

Re: [PATCH 4/4] REST: Add submission relations

On 30.12.19 21:28, Lukas Bulwahn wrote: > On Mo., 30. Dez. 2019 at 11:41, Mete Polat wrote: > >> Hi Stephen, >> >> On 27.12.19 18:48, Stephen Finucane wrote: >>> On Sat, 2019-12-07 at 17:46 +0100, Mete Polat wrote: >>>> View relations and add/up

Re: [PATCH v5] models, templates: Add submission relations

ghts? > We could possibly use request.path to extract the current API version and tell our queryset to filter out our unwanted events. Or am I missing something here? Best regards, Mete >> Signed-off-by: Mete Polat >> [dja: address some review comments from Stephen, add an ad

[PATCH] REST: Fix duplicate project queries

Eliminates duplicate project queries caused by calling get_absolute_url() in the embedded serializers. Following foreign keys with 'series__project' will cache the project of the series as well as the series itself. Signed-off-by: Mete Polat --- There are still some duplicates in va

Re: [PATCH] REST: Fix duplicate project queries

Hi Stephen, On 01.02.20 15:05, Stephen Finucane wrote: > On Wed, 2020-01-29 at 20:01 +0100, Mete Polat wrote: >> Eliminates duplicate project queries caused by calling >> get_absolute_url() in the embedded serializers. Following foreign keys >> with 'series__project'