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. 02 Dec, 2020 3 commits
  2. 08 Dec, 2020 1 commit
  3. 02 Dec, 2020 3 commits
  4. 27 Nov, 2020 1 commit
    • Anton Shestakov's avatar
      strip: remove experimental.prunestrip option · 8c5f2c37b911
      Anton Shestakov authored
      marmoute decided to drop it because it's "neither documented nor a good idea".
      
      This extensions was assemble to deal with Facebook willingness to check `hg
      strip` semantic for its user. Changing `hg strip` semantic is overall a pretty
      bad idea, because `stripping` is a specific operation, that is problematic in
      distributed version control but have a narrow set of valid usecase (eg:
      maintenance). Diverting user away from `prune` in favor of a modified `strip` is
      a bad idea, because it mask the legitimate `strip` usage and introduce confusion
      in user heads, The verb is not appropriate and the behavior of `prunestrip` does
      not match the one of vanillia `strip`.
      
      Facebook is no longer using this, and the lack of documentation is a good hint
      that nobody else is. So lets drop it.
      8c5f2c37b911
  5. 26 Nov, 2020 3 commits
  6. 25 Nov, 2020 1 commit
    • Anton Shestakov's avatar
      compat: wrap debugstrip from core hg if it exists · 716063c7a372
      Anton Shestakov authored
      Since the debugstrip command from core and strip command from the hgext.strip
      extension is now the same thing, we don't have to wrap them separately. Unless,
      of course, users have a copy of old (from hg 5.6 and earlier) hgext.strip
      laying around that they specifically want to use, but I don't think we want to
      support that use case.
      716063c7a372
  7. 23 Nov, 2020 1 commit
  8. 19 Nov, 2020 1 commit
    • Martin von Zweigbergk's avatar
      tests: update with more detailed exit codes · e5d91fd1f319
      Martin von Zweigbergk authored
      CORE-TEST-OUTPUT-UPDATE: 21733e8c924f
      CORE-TEST-OUTPUT-UPDATE: 8d72e29ad1e0
      CORE-TEST-OUTPUT-UPDATE: e0dbfbd4062c
      CORE-TEST-OUTPUT-UPDATE: ebee234d952a
      CORE-TEST-OUTPUT-UPDATE: 527ce85c2e60
      CORE-TEST-OUTPUT-UPDATE: 3175b0e0058b
      CORE-TEST-OUTPUT-UPDATE: f96fa4de5055
      CORE-TEST-OUTPUT-UPDATE: 96ca817ec192
      e5d91fd1f319
  9. 16 Nov, 2020 1 commit
  10. 11 Nov, 2020 1 commit
  11. 29 Oct, 2020 1 commit
  12. 31 Oct, 2020 7 commits
  13. 30 Oct, 2020 2 commits
  14. 28 Oct, 2020 1 commit
  15. 25 Oct, 2020 1 commit
  16. 24 Oct, 2020 3 commits
  17. 14 Oct, 2020 3 commits
  18. 20 Oct, 2020 1 commit
  19. 14 Oct, 2020 1 commit
    • Pierre-Yves David's avatar
      topic: add a `exp….topic.linear-merge` option to allow some oedipus · 3946ee4ee3ae
      Pierre-Yves David authored
      If this option is set to `from-branch`, a user can call `hg merge some-topic`
      from a bare branch even if `some-topic` is a direct descendant of the current
      working copy parents. This was previously denied if the changesets was on the
      same branch, since the result would be an "oedipus merge".
      
      Some user have been requesting this, and this type of merge is one of Gitlab
      standard way of merging a "Merge Request". That new option will unlock issue
      `heptapod#200` and make this mode available for those who wants it.
      3946ee4ee3ae
  20. 15 Oct, 2020 1 commit
  21. 12 Oct, 2020 2 commits
  22. 11 Oct, 2020 1 commit