1. 07 Dec, 2018 1 commit
  2. 01 Mar, 2018 1 commit
  3. 15 Jan, 2018 1 commit
    • Arkadiusz Hiler's avatar
      urls: Use named URLs · 492485df
      Arkadiusz Hiler authored
      Using the quoted doted path to the view callable object
      (e.g. 'patchwork.views.projects') is going to be deprecated soon.
      Using either the actual callable or a named URL is recommended.
      
      Let future-proof urls.py by using the actual callables there and
      name all the URLs, so we can use the names everywhere else.
      Signed-off-by: Arkadiusz Hiler's avatarArkadiusz Hiler <arkadiusz.hiler@intel.com>
      492485df
  4. 16 May, 2016 1 commit
  5. 03 May, 2016 1 commit
  6. 01 Apr, 2016 2 commits
  7. 22 Feb, 2016 1 commit
  8. 18 Feb, 2016 2 commits
  9. 16 Feb, 2016 1 commit
  10. 26 Jan, 2016 1 commit
  11. 18 Dec, 2015 1 commit
  12. 23 Nov, 2015 1 commit
  13. 19 Nov, 2015 2 commits
  14. 14 Nov, 2015 1 commit
  15. 12 Nov, 2015 1 commit
  16. 03 Nov, 2015 3 commits
  17. 20 Oct, 2015 3 commits
  18. 27 May, 2015 1 commit
  19. 03 May, 2015 1 commit
  20. 07 May, 2014 1 commit
  21. 21 Apr, 2014 1 commit
  22. 20 Apr, 2013 1 commit
    • Jeremy Kerr's avatar
      bundles: Remove separate public bundle views · 5d0140ef
      Jeremy Kerr authored
      Having two views for bundles (public and non-public) can cause confusion
      when bundle owners want to share a URL; it's not obvious that the
      private URL isn't shareable.
      
      This change removes the private URLs, and puts all bundles under the
      /bundle/<username>/<bundlename>/ URL space. For non-public bundles, this
      will just 404 for non-owners.
      Signed-off-by: default avatarJeremy Kerr <jk@ozlabs.org>
      5d0140ef
  23. 30 Dec, 2012 1 commit
  24. 14 Apr, 2011 3 commits
    • Jeremy Kerr's avatar
      Add email opt-out system · 41f19b66
      Jeremy Kerr authored
      We're going to start generating emails on patchwork updates, so firstly
      allow people to opt-out of all patchwork communications.
      
      We do this with a 'mail settings' interface, allowing non-registered
      users to set preferences on their email address. Logged-in users can do
      this through the user profile view.
      Signed-off-by: default avatarJeremy Kerr <jk@ozlabs.org>
      41f19b66
    • Jeremy Kerr's avatar
      registration: use EmailConfimation rather than separate registration app · c2c6a408
      Jeremy Kerr authored
      Since we have infrastructure for email confirmations, we no longer need
      the separate registration app.
      
      Requires a migration script, which will delete all inactive users,
      including those newly added and pending confirmation. Use carefully.
      Signed-off-by: default avatarJeremy Kerr <jk@ozlabs.org>
      c2c6a408
    • Jeremy Kerr's avatar
      Use generic email confirmation object · 56e2243f
      Jeremy Kerr authored
      Rather than having a UserPerson-specific confirmation, add an
      EmailConfirmation object to allow multiple types of confirmations (eg,
      opt-out requests in future).
      
      To do this, we use a view (patchwork.views.confirm) that will call the
      type-specific view with the confirmation object.
      
      Also, add tests to check that the User/Person linkage system works.
      Signed-off-by: default avatarJeremy Kerr <jk@ozlabs.org>
      56e2243f
  25. 05 Apr, 2009 1 commit
  26. 23 Sep, 2008 1 commit
  27. 09 Sep, 2008 1 commit
  28. 08 Sep, 2008 3 commits
  29. 23 Aug, 2008 1 commit