Skip to content
Snippets Groups Projects
  1. Jun 25, 2013
  2. Jun 24, 2013
  3. Jun 29, 2013
  4. Jun 24, 2013
  5. Jun 23, 2013
  6. Jun 24, 2013
  7. Jun 23, 2013
  8. Jun 26, 2013
  9. Jun 20, 2013
    • Siddharth Agarwal's avatar
      test-pathencode: randomize length of each path component · ec17ddecdf64
      Siddharth Agarwal authored
      This makes it possible for long and short components to exist in the same path.
      This also makes shorter path components more likely. For
      randint(1, randint(1, n)), the likelihood that one sees a number k
      (1 <= k <= n) is 1/n * (\sum_{k=i}^n 1/i). This decreases with k, much like in
      the real world where shorter paths are more common than longer ones.
      
      The previous fix and this one together cause issue3958 to be detected by this
      test with reasonable frequency. When this test was run 100 times in a loop, the
      issue was detected 30 of those times.
      ec17ddecdf64
    • Siddharth Agarwal's avatar
      test-pathencode: reduce makepart length requirement by 1 · 9778c77f05d6
      Siddharth Agarwal authored
      This allows path components of length 1 to be generated.
      9778c77f05d6
    • Siddharth Agarwal's avatar
      pathencode: fix hashmangle short dir limit (issue3958) · 66da6e9feacd
      Siddharth Agarwal authored
      The Python version of this (see mercurial/store.py:_hashencode) copies path
      components up to a limit of maxshortdirslen bytes. The Python version does not
      consider the initial "dh/" to be part of the this, though, while the C version
      currently does. Adding len("dh/") == 3 to the limit for the C version brings it
      in line with the Python version.
      
      This was not caught by the randomized testing scheme in test-pathencode.py
      because of a couple of flaws with the test. Upcoming patches will fix those
      problems.
      66da6e9feacd
    • Matt Mackall's avatar
      docs: change description to synopsis in hgrc.5 · 6f3428c528b4
      Matt Mackall authored
      Spotted by Eric S. Raymond.
      6f3428c528b4
  10. May 02, 2013
    • Iulian Stana's avatar
      commit: amending with --close-branch (issue3445) · b500a663a2c7
      Iulian Stana authored
      You can't close a branch that hasn't got a head.
      newbranch + commit --close-branch must fail
      newbranch + commit + commit --amend --close-branch must fail
      
      You must not be allowed to close a branch that is not defined.
      b500a663a2c7
  11. Jun 06, 2013
    • Jordi Gutiérrez Hermoso's avatar
      doc: make it easier to read how to enable extensions · da16d21cf4ed
      Jordi Gutiérrez Hermoso authored
      We tell people all the time that enabling extensions is not a scary
      thing to do, but we don't make it easy enough for an absolute novice
      to do so. When they see a suggestion to do "hg extfoo bar", the error
      message tells them "see hg help extensions", but that help page
      doesn't actually tell them where configuration files are.
      
      Furthermore, the big warning about why extensions aren't enabled by
      default should be pushed down a little bit. Most of the extensions
      shipped by hg are not all that scary, and some very basic and useful
      cosmetic extensions like graphlog, color, pager, and progress, should
      be enabled for many hg users.
      da16d21cf4ed
    • Jordi Gutiérrez Hermoso's avatar
      doc: reword "config file" to "configuration file" · 73066ba46ec5
      Jordi Gutiérrez Hermoso authored
      While we do use the abbreviation "config" elsewhere in the docs, the
      phrase "configuration file" is always written out in full, except in
      this location in phases.txt.
      73066ba46ec5
  12. Jun 05, 2013
  13. Jun 01, 2013
  14. May 31, 2013
  15. May 28, 2013
  16. May 27, 2013
  17. May 30, 2013
  18. May 23, 2013
  19. May 21, 2013
  20. May 23, 2013
    • Matt Mackall's avatar
      b592fd33233a
    • Durham Goode's avatar
      blackbox: fix blackbox causing exceptions in tests · 6d6f148cada9
      Durham Goode authored
      In the tests some scripts call reposetup with the base ui instead of the
      one the extensions have modified.  This causes an exception in
      blackbox.reposetup since it expected a method to be there. So I just
      check for it first. This only happened when the blackbox extension
      was enabled during tests.
      6d6f148cada9
    • Durham Goode's avatar
      blackbox: fix recording exit codes (issue3938) · 41e39a0299cb
      Durham Goode authored
      Previously the blackbox wrapped runcommand, but this failed to see the error
      codes that were created if an exception occurred. I moved that logging to now
      wrap _runcatch, so it can observe and log the actual error code (such as when
      a user ctrl+c's during a command).
      
      Updated the tests as well. Tested the change by running all the tests with the
      blackbox extension enabled and verifying nothing broke (aside from things that
      printed what extensions were enabeld).
      
      The progress tests are affected by calls to time.time() so they needed to be
      updated to pass.
      41e39a0299cb
  21. May 21, 2013
  22. May 14, 2013
  23. May 12, 2013
    • Nikolaj Sjujskij's avatar
      i18n-ru: fix patchbomb confirmation prompt (issue3929) · 0890e6fd3e00
      Nikolaj Sjujskij authored
      Recognize y(es) and (n)o as valid input, for user not to have to switch
      keyboard layout twice (`hg email -o ...` is Latin, whereas д(а)/н(ет) are not).
      Use capital Y/N letters in prompt, otherwise y could be mistaken for у, and n
      - for п.
      0890e6fd3e00
Loading