clandmeter/patchwork/templates, branch master

Move to a more recent django project structure

2015-05-27T02:26:41+00:00

This change updates patchwor to the newer project struture: we've moved
the actual application out of the apps/ directory, and the
patchwork-specific templates to under the patchwork application.

This gives us the manage.py script in the top-level now.

Signed-off-by: Jeremy Kerr

Integrate 'django.contrib.staticfiles'

2015-05-03T05:46:52+00:00

Rather than providing a custom solution for serving static files, use
the solution provided in the upstream Django source.

This allows us to remove the top-level 'urls.py' file.

Signed-off-by: Stephen Finucane 
Signed-off-by: Jeremy Kerr

Resolve removed 'AUTH_PROFILE_MODULE' setting

2015-05-03T05:46:52+00:00

The 'AUTH_PROFILE_MODULE' setting, and the 'get_profile()' method on
the 'User' model are removed in Django 1.7. This causes errors when
using Patchwork with Django 1.7+.

There are three changes necessary:

 * Replace profile model's 'ForeignKey' with a 'OneToOneField'
 * Remove all 'get_profile()' calls
 * Delete 'AUTH_PROFILE_MODULE' settings from 'settings.py'

These changes are discussed here:

    http://deathofagremmie.com/2014/05/24/retiring-get-profile-and-auth-profile-module/

Django 1.6 also introduces two other notable changes:

 * The 'XViewMiddleware' module has been moved
 * A new test runner has been introduced

It is not possible to fix these issues without breaking compatibility
with Django 1.5. As a result they have been ignored and must be
resolved in a future release.

Signed-off-by: Stephen Finucane 
Signed-off-by: Jeremy Kerr

Make the submitter name link to a query for that submitter

2015-05-03T05:43:42+00:00

Currently the submitter name is rendered as a mailto: link. This is
possibly useful in some circumstances, but in my experience is not
usually what I want. Although it opens a mail to the submitter, it
doesn't include any of the patch context, so is not very helpful.

Instead the submitter link can be a link to a query for patches by that
submitter. In my experience that is more useful, ie. when looking at a
single patch for a submitter you can then quickly get the list of all
patches by them.

So do that conversion.

In order to do it we need to know the current project, so that becomes a
parameter to personify. I believe the url reversal is correct, though
it's not pretty, and pulling SubmitterFilter.param out feels a little
wrong, but is the best solution I could come up with.

Signed-off-by: Michael Ellerman 
Signed-off-by: Jeremy Kerr

templates: fixup HTML tags

2014-07-04T00:52:49+00:00

These tags aren't matched appropriately.

There may well be others, but I caught these by a mix of eyes and
Firefox's source viewer.

Signed-off-by: Brian Norris 
Signed-off-by: Jeremy Kerr

pwclient: accept more than one project in ~/.pwclientrc

2014-07-04T00:37:46+00:00

Currently, given the format of ~/.pwclientrc, pwclient can only
really act on a single project, as ~/pwclientrc can only contain
the configuration for a single project.

Although the -p options comes in handy to specify a project
different from the one configured in ~/.pwclientrc, this only works
if it is hosted on the same server. As soon as one needs to switch
server, it is necessary to edit ~/pwclientrc.

This can be quite inefficient when dealing with many projects, hosted
on different servers.

Change the format of ~/.pwclientrc so it is possible to define more
than one project, and for each project, specify an URL and credentials.

The new format is like:

    [options]
    default = project-A

    [project-A]
    url = http://my.patchwork.server/path/to/xmlrpc
    username = that-is-me
    password = secret

    [other-project]
    url = http://you.get/the/idea
    username = someone
    password = 1234

This has the advantage of not changing the options to pwclient, so
the user experience is unmodified.

If a ~/.pwclentrc exists in the old format, it is automatically
converted over to the new format, and the previous one is saved as
~/.pwclientrc.orig. Upon conversion, no action is made, pwclient just
exits (with return-code 1) to inform the user to review the conversion.

Signed-off-by: "Yann E. MORIN" 
Signed-off-by: Jeremy Kerr

templates: display projects as inline-block elements

2014-05-07T03:26:45+00:00

... rather than one long list.

Signed-off-by: Jeremy Kerr

Django 1.5 compatibility fixes

2013-10-13T06:00:18+00:00

Django 1.5 wants plenty of quotes scattered over the templates.

Signed-off-by: Ralf Baechle 
Signed-off-by: Jeremy Kerr

views/base: Implement limit for submitter autocompletion

2013-10-13T05:04:31+00:00

Add a limit parameter to the completion view, and pass a limit of 20
results in the javascript.

Signed-off-by: Jeremy Kerr

notifications: add project name to patch update notification

2013-06-16T09:25:44+00:00

Based on a feature request & patch from Wolfram Sang
.

Notifications may span multiple projects, so include a summary in the
subject line, and detail in the header.

Signed-off-by: Jeremy Kerr