Age | Commit message (Collapse) | Author |
|
Since the upstream main website now handles secondary email addresses,
centralize the handling to there. This removes the local handling
completely, except that we store them in the database. The new
push-changes API ensures that they are kept in sync with upstream.
|
|
|
|
Need to change old migrations not to indicate we need new ones.
|
|
|
|
|
|
|
|
|
|
This is rquired as part of the move to a newer Django, and works fine on
older versions too
|
|
Patch in 2e41b31654b80aeb3e6037fc0b31422c951040c7 only handled From and
missed the ohher tields. To make this cleaner, move the escpaping code
into the UserWrapper class.
Reported by Dagfinn Ilmari Mannsåker, but not using his patch
|
|
This makes it possible to receive notifications (via email) when a patch
has been updated.
It's possible to subscribe to notifications on a specific patch. It is also
possible to set the user profile up so that one receives notifications for
all patches where one is author, reviewer or committer on.
Notifications are, of course, only sent when other people make modifications
to the entry.
|
|
|
|
Should've been done with the migration to django 1.8, but better late
than never...
|
|
|
|
|
|
Instead of having inline stylesheets, put them all in a separate CSS
file. This really should've been done from the beginning, but was
clearly forgotten before deployment.
|
|
|
|
Each user can add a secondary email (well, more than one) and then pick
one of those when sending email.
Addresses are validated by sending a token to the newly added address,
with a link to click to confirm it. Only a fully confirmed address can
actually be used.
|