1. 07 Jul, 2020 1 commit
  2. 23 Apr, 2020 1 commit
  3. 25 Mar, 2020 1 commit
  4. 22 Oct, 2019 1 commit
  5. 05 Mar, 2019 1 commit
    • Arkadiusz Hiler's avatar
      views: Fix typo in dictionary key · cf1de39f
      Arkadiusz Hiler authored
      
      
      One extra "s" in "messages", which was causing the following exception
      when bulk updating patches with no patches selected:
      
        File "/srv/patchwork.freedesktop.org/lib/apache2/../../patchwork/views/__init__.py" in process_multiplepatch_form
          157.         context['messsages'] += ["No patches selected; nothing updated"]
      
        Exception Type: KeyError
        Exception Value: 'messsages'
      Signed-off-by: default avatarArkadiusz Hiler <arkadiusz.hiler@intel.com>
      cf1de39f
  6. 28 Feb, 2019 1 commit
  7. 13 Feb, 2019 1 commit
    • Arkadiusz Hiler's avatar
      HAX: email: Workaround FDO's header mangling · efad0307
      Arkadiusz Hiler authored
      
      
      FDO started respecting DMARC, which means it cannot freely resend emails
      without rewriting 'From:' header in some cases.
      
      So this:
        From: Author <original@mail>
      Changes to:
        From: Author via listname <listid@lists.freedesktop.org>
        Reply-To: Author <original@mail>
      
      Let's recognize that and unmangle it for authorship and mbox purposes.
      Signed-off-by: default avatarArkadiusz Hiler <arkadiusz.hiler@intel.com>
      efad0307
  8. 02 Jan, 2019 1 commit
  9. 30 May, 2018 1 commit
  10. 23 May, 2018 1 commit
    • Arkadiusz Hiler's avatar
      mbox: Use the 'From' header from the incoming email · 63b2762b
      Arkadiusz Hiler authored
      
      
      Currently all the patchwork-generated mboxes uses the name and email
      address extracted from the last patch that person sent. This is strange
      behaviour that leads to problem when a users puts additional information
      (e.g. sponsor) in the header or has changed their legal name.
      
      There's no silver bullet to address all the possible scenarios, and this
      behaviour causes a lot of confusion.
      
      Luckily we store the vanilla email headers the patch was sent out with
      in patch.headers. We can use that to stop the guess game and let the
      people to control how they are called for every patch.
      Signed-off-by: default avatarArkadiusz Hiler <arkadiusz.hiler@intel.com>
      63b2762b
  11. 16 Jan, 2018 1 commit
  12. 05 Apr, 2016 1 commit
  13. 18 Feb, 2016 3 commits
  14. 16 Feb, 2016 2 commits
  15. 04 Nov, 2015 1 commit
  16. 17 Sep, 2015 1 commit
  17. 05 Jun, 2015 2 commits
  18. 28 May, 2015 1 commit
    • Jeremy Kerr's avatar
      Add patch tag infrastructure · 3b8a61c6
      Jeremy Kerr authored
      
      
      This change add patch 'tags', eg 'Acked-by' / 'Reviewed-by', etc., to
      patchwork.
      
      Tag parsing is implemented in the patch parser's extract_tags function,
      which returns a Counter object of the tags in a comment. These are
      stored in the PatchTag (keyed to Tag) objects associated with each
      patch.
      
      We need to ensure that the main patch lists do not cause per-patch
      queries on the Patch.tags ManyToManyField (this would result in ~500
      queries per page), so we introduce a new QuerySet (and Manager) for
      Patch, adding a with_tag_counts() method to populate the tag counts in a
      single query.
      
      As users may be migrating from previous patchwork versions (ie, with no
      tag counts in the database), we add a 'retag' management command.
      Signed-off-by: default avatarJeremy Kerr <jk@ozlabs.org>
      3b8a61c6
  19. 27 May, 2015 1 commit
  20. 24 Jul, 2014 1 commit
  21. 08 May, 2014 1 commit
    • Jeremy Kerr's avatar
      views/generic_list: reduce number of queries in list rendering · 2c2f5e99
      Jeremy Kerr authored
      
      
      Currently, we do two database queries per patch on a list view; one to
      retrieve the submitter, and one for the state.
      
      This patch adds a .select_related to fetch for the submitter and state,
      and a .defer() to prevent loading large amounts of text data from the
      patch content and headers.
      
      This gives a significant reduction in the work per request. For a
      paginated list view (ie 100 patches per page):
      
                                before        after
        User                   1344 ms       228 ms
        System                  170 ms        25 ms
        Total                  1514 ms       253 ms
        Elapsed                1605 ms       274 ms
      
        Context switch (vol)   4206           40
        Context switch (invol)  326           75
      
        SQL queries             212           15
        Longest query            13 ms         5 ms
        Total query time        121 ms        20 ms
      Signed-off-by: default avatarJeremy Kerr <jk@ozlabs.org>
      2c2f5e99
  22. 21 Apr, 2014 1 commit
  23. 16 Jun, 2013 1 commit
  24. 10 Jun, 2013 2 commits
  25. 30 Dec, 2012 1 commit
  26. 14 Apr, 2011 2 commits
  27. 09 Mar, 2011 1 commit
    • Jeremy Kerr's avatar
      views: use id__in = get_patch_ids() to get the modified patch set · 25f3514a
      Jeremy Kerr authored
      
      
      Currently, we generic_list processes patches in order of the patch_id:X
      parameter, which is arbitrarily decided by the browser.
      
      By using id__in, we get patches sorted by the default Patch model
      ordering. This means that the (arbitrary) order of get_patch_ids()
      doesn't affect the ordering of patches that we process, and bundles
      are created with a reasonable default patch order.
      Signed-off-by: default avatarJeremy Kerr <jk@ozlabs.org>
      25f3514a
  28. 08 Feb, 2009 1 commit
  29. 20 Sep, 2008 1 commit
  30. 23 Aug, 2008 1 commit
  31. 21 Aug, 2008 2 commits