This instance will be upgraded to Heptapod 0.23.2 on 2021-08-05 at 11:00 UTC+2 (a few minutes of down time)

  1. 04 Nov, 2020 1 commit
  2. 23 Jun, 2020 1 commit
  3. 07 Oct, 2020 2 commits
  4. 29 Oct, 2020 1 commit
    • Dan Villiom Podlaski Christiansen's avatar
      commit: warn the user when a commit already exists · 976b26bdd0d8
      Dan Villiom Podlaski Christiansen authored
      Sometimes, a commit will result in an exact match of a preexisting
      commit, and if that commit isn't a branch head, hg will incorrectly
      note that it created a new head. Instead, we should warn the user that
      commit already existed in the repository.
      
      In practice, this bug is rather uncommon, and will only occur when the
      usr explicitly sets the date.
      
      Please note that this commit contains an API change to
      cmdutil.commitstatus()
      
      Differential Revision: https://phab.mercurial-scm.org/D9257
      976b26bdd0d8
  5. 06 Oct, 2020 1 commit
    • Jörg Sonnenberger's avatar
      revlog: don't cache parsed tuples in the C module · 4404f129341e
      Jörg Sonnenberger authored
      A cached entry creates ~8 Python objects per cached changeset, which
      comes to around 200 Bytes per cached changeset on AMD64. Especially for
      operations that touch a lot of changesets, that can easily sum up to
      more than a 100MB of memory. Simple tests on large repositories show
      <2% runtime penalty for ripping out the cache, even for cache heavy
      operations like "hg log" for all revisions.
      
      Differential Revision: https://phab.mercurial-scm.org/D9155
      4404f129341e
  6. 26 Oct, 2020 1 commit
  7. 29 Oct, 2020 1 commit
  8. 24 Oct, 2020 1 commit
    • Matt Harbison's avatar
      repoview: only pin obsolete wdir parents while there are unresolved conflicts · 341e014fe0fb
      Matt Harbison authored
      I noticed after doing an update from an obsolete revision with a dirty wdir that
      the obsolete commit stayed visible for no obvious reason.  It was decided in
      85b03b1e4715 not to clear mergestate once all of the conflicts were resolved, in
      order to allow re-resolving.  Since the point of pinning the obsolete parents
      was to allow resolving in the first place (aaeccdb6e654), it makes sense to also
      gate it on whether or not there are any remaining files to resolve.  This might
      result in pinning again if files are marked unresolved again, but that seems
      reasonable, given that it still solves the original issue.
      
      Note that this isn't purely cosmetic- pushing with a pinned obsolete revision is
      likely to cause complaints about pushing multiple heads or other unexpected
      errors.  So the faster it comes out of that state, the better.
      
      Differential Revision: https://phab.mercurial-scm.org/D9248
      
      --HG--
      branch : stable
      341e014fe0fb
  9. 28 Oct, 2020 1 commit
  10. 23 Oct, 2020 2 commits
  11. 29 Oct, 2020 1 commit
  12. 17 Oct, 2020 1 commit
  13. 16 Oct, 2020 7 commits
  14. 13 Oct, 2020 1 commit
  15. 21 Oct, 2020 1 commit
  16. 29 Oct, 2020 1 commit
    • Martin von Zweigbergk's avatar
      templates: include all non-branch namespaces in default one-line summary · e9555305c5c6
      Martin von Zweigbergk authored
      I left out branches and custom namespaces on purpose from D9252
      because I figured that people like us (Google) who have custom
      namespaces can also have custom configs. However, I just realized that
      this makes everyone with the topic extension lose the topic they've
      had in rebase output for a long time (ever since someone was nice
      enough to add it in D741). Sorry about the churn.
      
      The more generic template couldn't easily keep the "log.bookmark"
      label in the template because the namespace is called "bookmarks"
      (plural). That means that we can't be compatible with users' existing
      configs for "log.bookmark", so I decided to change the labels to be in
      a brand-new "oneline-summary" namespace.
      
      Differential Revision: https://phab.mercurial-scm.org/D9262
      e9555305c5c6
  17. 17 Oct, 2020 1 commit
  18. 20 Oct, 2020 1 commit
  19. 19 Oct, 2020 1 commit
  20. 18 Oct, 2020 1 commit
  21. 12 Oct, 2020 1 commit
  22. 07 Oct, 2020 1 commit
    • Pulkit Goyal's avatar
      tags: add safety check for len(record) while reading hgtagsfnodescache · 225e513c444e
      Pulkit Goyal authored
      I am trying to fix a breakage where somehow we end up getting a node of 12
      length from `getfnode()`. Understanding the hgtagsfnodescache code, it seems
      highly unlikely that it can happen unless one of `mctx.readfast().get()` or
      `ctx.filenode()` is returning a node of 12 length.
      
      For safety, I think it's better to add a check to make sure that record which we
      are parsing is of same length we are expecting otherwise we consider that as
      invalid record.
      
      Differential Revision: https://phab.mercurial-scm.org/D9169
      225e513c444e
  23. 14 Oct, 2020 2 commits
  24. 15 Oct, 2020 1 commit
    • Pierre-Yves David's avatar
      clonebundles: move a bundle of clone bundle related code to a new module · 74271829ddc0
      Pierre-Yves David authored
      In the process on general clone bundle automatically, we need to make some
      function available more widely. This is a good opportunity to extract a
      significant amount of code from `mercurial.exchange` into a new
      `mercurial.bundlecaches`. This make `mercurial.exchange` move under the 3K line
      range (hooray…).
      
      The module is called `bundlecaches` because I expect it to be eventually useful
      for more than just clone bundle (like pull bunbles).
      
      Differential Revision: https://phab.mercurial-scm.org/D9208
      74271829ddc0
  25. 05 Oct, 2020 1 commit
  26. 13 Oct, 2020 2 commits
  27. 15 Oct, 2020 1 commit
  28. 05 Oct, 2020 1 commit
    • Jörg Sonnenberger's avatar
      unbundle: free temporary objects after use · 44d84b726c8a
      Jörg Sonnenberger authored
      This reduces peak RSS for larger unbundle operations by ~30 Bytes per
      changeset on AMD64. This can't be a direct delete for Python 2.7, so
      reset the object instead and leave a comment.
      
      The efilesset object can't be deleted as it is referenced by the local
      onchangelog function and Python 2.7 rejects a delete on the existance of
      a nested scope.
      
      Differential Revision: https://phab.mercurial-scm.org/D9153
      44d84b726c8a
  29. 13 Oct, 2020 1 commit
  30. 14 Oct, 2020 1 commit