1. 02 Oct, 2015 1 commit
  2. 25 Nov, 2015 1 commit
  3. 24 Nov, 2015 1 commit
  4. 27 Nov, 2015 1 commit
  5. 24 Nov, 2015 3 commits
  6. 25 Nov, 2015 1 commit
  7. 22 Nov, 2015 1 commit
    • Gregory Szorc's avatar
      ui: avoid needless casting to a str · f04bd381e8c0
      Gregory Szorc authored
      In many cases, we don't need to cast to a str because the object will
      be cast when it is eventually written.
      
      As part of testing this, I added some code to raise exceptions when a
      non-str was passed in and wasn't able to trigger it. i.e. we're already
      passing str into this function everywhere, so the casting isn't
      necessary.
      f04bd381e8c0
  8. 24 Nov, 2015 1 commit
  9. 22 Nov, 2015 3 commits
    • Gregory Szorc's avatar
      color: evaluate labels at write time · 717b75ae5bb0
      Gregory Szorc authored
      Previously, we stored 2-tuples of text and label in a list and then
      evaluated the labels when the buffer was popped. After this patch,
      we evaluate the labels at write time and do a simple join when the
      buffer is popped.
      
      This patch appears to have no impact on performance, despite creating
      fewer 2-tuples and having fewer strings hanging around in memory.
      717b75ae5bb0
    • Gregory Szorc's avatar
      cmdutil: pass labeled=True to pushbuffer() · c57ebef70f6f
      Gregory Szorc authored
      This doesn't yet change behavior because labeling is still performed
      at popbuffer time.
      
      Surprisingly, this is the only in-tree consumer that passes
      labeled=True.
      c57ebef70f6f
    • Gregory Szorc's avatar
      ui: track label expansion when creating buffers · 6ef17697b03d
      Gregory Szorc authored
      As part of profiling `hg log` performance, I noticed a lot of time
      is spent in buffered writes to ui instances. This patch starts a series
      that refactors buffered writes with the eventual intent to improve
      performance.
      
      Currently, labels are expanded when buffers are popped. This means
      we have to preserve the original text and the label until we render
      the final output. This is avoidable overhead and adds complexity
      since we're retaining state.
      
      This patch adds functionality to ui.pushbuffer() to declare whether
      label expansion should be active for the buffer. Labels are still
      evaluated during buffer pop. This will change in a subsequent
      patch.
      
      Since we'll need to access the "expand labels" flag on future write()
      operations, we prematurely optimize how the current value is stored
      to optimize for rapid retrieval.
      6ef17697b03d
  10. 24 Nov, 2015 8 commits
  11. 02 Nov, 2015 1 commit
    • Pierre-Yves David's avatar
      format: create new repository as 'generaldelta' by default · 41d3e307a7c1
      Pierre-Yves David authored
      Since we have pushed back the performance issue related to general delta behind
      another configuration (Still off by default), we can safely create new
      repository with general delta support. As client are compatible with it since
      Mercurial 1.9 (4.5 years ago) I do no expect any significant compatibility
      issues.
      41d3e307a7c1
  12. 23 Nov, 2015 3 commits
  13. 16 Nov, 2015 1 commit
  14. 21 Nov, 2015 1 commit
  15. 16 Nov, 2015 1 commit
  16. 23 Nov, 2015 1 commit
  17. 17 Nov, 2015 1 commit
    • Mateusz Kwapich's avatar
      histedit: add an experimental base action · d50ff8f4891f
      Mateusz Kwapich authored
      This is a first (very simple) version of the histedit base action.
      It works well in common usecases like rebasing the whole stack and
      spliting the stack.
      
      I don't see any obvious edge cases - but probably there is more than one.
      That's why I want to keep it behind experimental.histeditng config knob
      for now. I think on knob for all new histedit behaviors is better because
      we will test all of them together and testers will need to turn it on only
      once to get all new nice things.
      d50ff8f4891f
  18. 18 Nov, 2015 1 commit
  19. 13 Nov, 2015 1 commit
    • Mateusz Kwapich's avatar
      histedit: add forceother constraint · 6d5d7ac41ef4
      Mateusz Kwapich authored
      For the future 'base' action in histedit we need a verification
      constraint which will not allow using this action with changes
      that are currently edited.
      6d5d7ac41ef4
  20. 18 Nov, 2015 1 commit
    • Mateusz Kwapich's avatar
      histedit: make verification configurable · 4898e442f392
      Mateusz Kwapich authored
      Before we can add a 'base' action to histedit need to change verification
      so that action can specify which steps of verification should run for it.
      
      Also it's everything we need for the exec and stop actions implementation.
      
      I thought about baking verification into each histedit action (so each
      of them is responsible for verifying its constraints) but it felt wrong
      because:
       - every action would need to know its context (eg. the list of all other
         actions)
       - a lot of duplicated work will be added - each action will iterate through
         all others
       - the steps of the verification would need to be extracted and named anyway
         in order to be reused
      
      The verifyrules function grows too big now. I plan to refator it in one of
      the next series.
      4898e442f392
  21. 13 Nov, 2015 1 commit
  22. 20 Nov, 2015 1 commit
  23. 21 Nov, 2015 5 commits