Skip to content
Snippets Groups Projects
  1. Jul 25, 2013
  2. Jul 22, 2013
  3. Jul 25, 2013
  4. Jul 21, 2013
  5. Jul 20, 2013
  6. Jul 24, 2013
  7. May 12, 2013
    • durin42's avatar
      hgweb: force connection close on early response · 60e060f4faa9
      durin42 authored
      Not all WSGI servers close the socket when an early response is sent
      to a large POST request, which can cause the server to interpret the
      already-sent request body as an incoming (but hopelessly invalid)
      request.
      60e060f4faa9
  8. Jul 24, 2013
    • Alexander Plavin's avatar
      hgweb: fix incorrect revisions count in graph (issue3977) · 8cfa3a3664a5
      Alexander Plavin authored
      Actual amount of revisions is used now instead of their numbers in the repo
      before to deal with skipped numbers correctly.
      8cfa3a3664a5
    • Alexander Plavin's avatar
      hgweb: fix incorrect way to count revisions in log (issue3977) · 002b711a3e8a
      Alexander Plavin authored
      Actual amount of revisions is used now instead of their numbers in the repo
      before to deal with skipped numbers correctly.
      This iterates starting from the newest revision (which is shown on top)
      yielding up to the specified count, instead of the reversed order used before.
      Effect of this change on efficiency is negligible, when the same changesets are
      returned.
      002b711a3e8a
    • Alexander Plavin's avatar
      hgweb: always start graph with the revision in url · 02c71f96eb6c
      Alexander Plavin authored
      It is the same fix for graph command, as was recently for log. This makes the
      specified revision be always on top of the graph view.
      Before the patch, for example with repo having revisions 0, 1, 2, 3 and revision
      in url being '2', all revisions were shown and the specified one wasn't
      the first.
      02c71f96eb6c
  9. Jul 25, 2013
  10. Jul 24, 2013
  11. Jul 25, 2013
  12. Jul 24, 2013
  13. Jul 23, 2013
  14. Jul 21, 2013
  15. Jul 19, 2013
  16. Jul 12, 2013
    • Shun-ichi GOTO's avatar
      osutil: consider WindowsError's behaviour to support python 2.4 on Windows · 004f965630d9
      Shun-ichi GOTO authored
      This change treat the ESRCH error as ENOENT like WindowsError class
      does in python 2.5 or later. Without this change, some try..execpt
      code which expects errno is ENOENT may fail. Actually hg command does
      not work with python 2.4 on Windows.
      
      CreateFile() will fail with error code ESRCH
      when parent directory of specified path is not exist,
      or ENOENT when parent directory exist but file is not exist.
      Two errors are same in the mean of "file is not exist".
      So WindowsError class treats error code ESRCH as ENOENT
      in python 2.5 or later, but python 2.4 does not.
      
      Actual results with python 2.4:
      >>> errno.ENOENT
      2
      >>> errno.ESRCH
      3
      >>> WindowsError(3, 'msg').errno
      3
      >>> WindowsError(3, 'msg').args
      (3, 'msg')
      
      And with python 2.5 (or later):
      >>> errno.ENOENT
      2
      >>> errno.ESRCH
      3
      >>> WindowsError(3, 'msg').errno
      2
      >>> WindowsError(3, 'msg').args
      (3, 'msg')
      
      Note that there is no need to fix osutil.c because it never be used
      with python 2.4.
      004f965630d9
  17. Jul 17, 2013
    • Matthew Turk's avatar
      churn: split email aliases from the right · 68f7129af6a8
      Matthew Turk authored
      This splits churn email aliases from the right, to enable incorrectly-specified
      addresses that include equal signs to be mapped to correct addresses.  This
      will enable aliasing of bad addresses (typically typos) such as:
      
      sername=myusername
      
      that appear in the churn output through a churn alias such as:
      
      sername=myusername = myusername
      
      whereas previously splitting from the left would not enable this behavior.
      68f7129af6a8
  18. Jul 14, 2013
  19. Jul 12, 2013
    • Alexander Plavin's avatar
      hgweb: always start log with searched revision · a87d9102f7af
      Alexander Plavin authored
      This makes the specified revision be always on top of the list.
      Before the patch, for example with repo having revisions 0, 1, 2, 3 and user
      searching for '2', all revisions were shown and the specified one wasn't
      the first.
      a87d9102f7af
  20. Jul 01, 2013
  21. Jul 19, 2013
Loading