Skip to content
Snippets Groups Projects
  1. Mar 14, 2019
    • Pierre-Yves David's avatar
      manifestcache: use `wcache` directory for manifest cache · e4ac7e63c213
      Pierre-Yves David authored
      The manifest full text cache is tightly related to the working copy. We should
      use the `wcache` directory for it, instead of the `cache`. Otherwise, multiple
      shares would keep overwriting each other cache entry and we loose its benefit.
      
      This is also more consistent with the fact this cache file is protected by
      `wlock`.
      e4ac7e63c213
  2. Mar 15, 2019
  3. Mar 14, 2019
  4. Mar 15, 2019
  5. Mar 14, 2019
  6. Mar 15, 2019
  7. Mar 14, 2019
    • Gregory Szorc's avatar
      packaging: don't bundle DLLs in py2exe library.zip for x86 builds · d6e3c16d48ab
      Gregory Szorc authored
      I had ported the x86/x64 behavior difference from the Inno
      Setup installer files. Why things were this way, I'm not sure.
      
      The WiX configuration files are expecting to have standalone
      DLL files for both configurations. And the 32-bit WiX installers
      were broken due to missing DLLs.
      
      Let's standardize on standalone DLL files on all configurations
      for consistency. I /think/ this will be faster, as I /think/
      py2exe binaries would have to extract the DLL to a temporary file
      in order to load it. But I'm not 100% sure about that.
      
      Differential Revision: https://phab.mercurial-scm.org/D6135
      d6e3c16d48ab
  8. Mar 15, 2019
  9. Mar 13, 2019
  10. Mar 09, 2019
  11. Mar 14, 2019
  12. Dec 27, 2018
  13. Mar 11, 2019
  14. Feb 13, 2019
    • Sushil Khanchi's avatar
      copies: handle a case when both merging csets are not descendant of merge base · 7694b685bb10
      Sushil Khanchi authored
      This patch fix the behaviour of fullcopytracing algorithm in the case
      when both the merging csets are not the descendant of merge base.
      Although it seems to be the rare case when both the csets are not
      descendant of merge base. But it can be seen in most of cases of
      content-divergence in evolve extension, where merge base is the common
      predecessor.
      Previous patch added a test where this algorithm can fail to continue
      because of an assumption that only one of the two csets can be dirty.
      This patch fix that error.
      
      For refrence I suggest you to look into the previous discussion held
      on a patch sent by Pulkit: https://phab.mercurial-scm.org/D3896
      
      Differential Revision: https://phab.mercurial-scm.org/D5963
      7694b685bb10
  15. Feb 14, 2019
    • Sushil Khanchi's avatar
      copies: add test that makes both the merging csets dirty and fails · fc4b7a46fda1
      Sushil Khanchi authored
      This patch is a part of series which is about the case when both the merging
      csets are not descendant of merge base. The existing code assumes if c1 is
      dirty there shouldn't be any partial copies from c2 i.e both2['incomplete']
      and same for c2, if c2 is dirty both1['incomplete'] should be empty,
      but this is not the right assumption.
      Now as we know we can have both c1 and c2 dirty at the same time, it
      is possible that c1 is dirty and both2['incomplete'] has some value.
      Or if c2 is dirty and both1['incomplete'] has some value.
      
      Added test shows that because of this assumption it could fail.
      
      Differential Revision: https://phab.mercurial-scm.org/D5962
      fc4b7a46fda1
    • Sushil Khanchi's avatar
      copies: add test that makes both the merging csets dirty and run w/o error · cbdd2b56d4c3
      Sushil Khanchi authored
      This series of patches is to cover a case in fullcopytracing algorithms
      where both the merging csets are not descendant of merge base.
      
      In this algorithm we call a merging cset "dirty" if that cset is not the
      descendant of merge base. That said, added test in this patch cover case
      when both the merging csets are "dirty".
      
      Actually this case of "both dirty" was encountered by Pulkit when he was
      working on content-divergence where it is possible that both the csets
      are not descendant of merging base.
      For reference you can look into: https://phab.mercurial-scm.org/D3896
      
      As this test run fine without any error and correctly traced the copies, I
      added this test to make sure that it doesn't break even after I will modify
      some code in next patches to fix an error. Next patch adds the tests where
      this algorithm throws an error for the same case of "both dirty".
      
      Differential Revision: https://phab.mercurial-scm.org/D5961
      cbdd2b56d4c3
  16. Mar 10, 2019
Loading