[PATCH 1/4] INSTALL: adopt PYTHONPATH

Signed-off-by: Andreas Bießmann --- docs/INSTALL |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/INSTALL b/docs/INSTALL index 91c6081..e5f88e8 100644 --- a/docs/INSTALL +++ b/docs/INSTALL @@ -128,7 +128,7 @@ in brackets): Then, get patchwork to create its tabl

Re: Make Acked/Reviewd/Tested-by tags visible

Dear Jeremy Kerr, On Tue, 12 Nov 2013 08:37:26 +0800, Jeremy Kerr wrote: > > We would like to suggest that the web GUI and the pwclient CLI both > > display such tags besides each patch, a bit like (hypotetical output of > > pwclient): > > > > ID Tags State Subject > > 123456 A

[PATCH 2/4] settings.py: use python to find ROOT_DIR

Signed-off-by: Andreas Bießmann --- apps/settings.py |4 +--- docs/INSTALL |7 --- 2 files changed, 1 insertion(+), 10 deletions(-) diff --git a/apps/settings.py b/apps/settings.py index 43a37d8..4e09a29 100644 --- a/apps/settings.py +++ b/apps/settings.py @@ -68,9 +68,7 @@ ROOT_

[PATCH 3/4] tests/mboxviews: test for unchanged postscript

Currently a patch containing postscript is always modified in patch_to_mbox() compared to the input patch. A comment containing 'some comment\n---\n some/file | 1 +' will be changed to 'some comment\n\n---\nsome/file | 1 +\n' which is annoying. This patch adds a test to detect that, a follow up p

[PATCH 4/4] views: fix patch_to_mbox() for postscript

Before we changed the comment 'some comment\n---\n some/file | 1 +' to 'some comment\n\n---\nsome/file | 1 +\n'. Now we pass this comment unchanged. Signed-off-by: Andreas Bießmann --- apps/patchwork/views/__init__.py |7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/

Re: Make Acked/Reviewd/Tested-by tags visible

On 12/11/13 07:58, Thomas Petazzoni wrote: Dear Jeremy Kerr, On Tue, 12 Nov 2013 08:37:26 +0800, Jeremy Kerr wrote: We would like to suggest that the web GUI and the pwclient CLI both display such tags besides each patch, a bit like (hypotetical output of pwclient): ID Tags State

suggestion: more information on project page

Could you add a link to a version of the code visible within the browser? For those that do not have git installed. (I finally found one on a mirror on https://bitbucket.org/bos/patchwork.) And maybe also one to the documentation? (The doc directory viewable in browser is good enough.) Greetings,

Re: [Buildroot] Make Acked/Reviewd/Tested-by tags visible

Hi, On Tue, Nov 12, 2013 at 7:58 AM, Thomas Petazzoni wrote: [..] >> Other projects have different policies for their tagging (some require 3 >> acks, for example), which will introduce a little complexity there too, >> but that's not insurmountable either. > > Another thing that comes to mind is