Skip to content
Snippets Groups Projects
  1. Apr 05, 2022
  2. Mar 22, 2022
  3. Apr 05, 2022
  4. Apr 04, 2022
    • Pierre-Yves David's avatar
      upgrade: split some logic from UpgradeOperation · 566066826e7c
      Pierre-Yves David authored
      The logic for automatic-upgrade and the upgrade-repo should be able to use the
      same code. However that code often need an UpgradeOperation object to function.
      So we start spliting the Operation into a minimal component that we will be
      able to reuse outside of the "classic" upgrade path.
      
      We will put the base-class to use in the next changeset.
      
      Differential Revision: https://phab.mercurial-scm.org/D12612
      566066826e7c
  5. Apr 05, 2022
    • Pierre-Yves David's avatar
      auto-upgrade: introduce a way to auto-upgrade to/from share-safe · 2ab79873786e
      Pierre-Yves David authored
      This is the first "automatic-upgrade" capability. In the following commits,
      similar features are coming for other "fast to upgrade" formats.
      
      This is different from the `safe-mismatch.source-not-safe` and
      `safe-mismatch.source-safe` configuration that deal with mismatch between a
      share and its share-source. Here we are dealing with mismatch between a
      repository configuration and its actual format.
      
      We will need further work for cases were the repository cannot be locked. A
      basic protection is in place to avoid  a infinite loop for now, but it will get
      proper attention in a later changeset.
      
      Differential Revision: https://phab.mercurial-scm.org/D12611
      2ab79873786e
  6. Apr 15, 2022
  7. May 10, 2022
  8. May 02, 2022
  9. May 13, 2022
  10. May 19, 2022
  11. May 16, 2022
    • Pierre-Yves David's avatar
      fix-ci: backed out changeset 308e45f7b455 · 22279b604a88
      Pierre-Yves David authored
      The  chg variant of the CI see a failure on `tests/test-narrow-pull.t`.
      Bisecting point the failure as starting at this small changeset…
      
      Backing it out, restore the CI on default. It was never broken on
      stable, which is even more puzzling.
      22279b604a88
  12. May 17, 2022
  13. May 16, 2022
    • Pierre-Yves David's avatar
      ci: do not trigger phabricator for merge-request · 477b5145e1a0
      Pierre-Yves David authored
      The fast the phabricator steps has a `rules` entry makes it selected for the
      special `merge_requests` pipelines. The other ones behave as default and are not
      selected tot the mrege_request pipelines.
      
      This result in a second pipeline to be created, with only the phabricator
      pipeline in it. Which usually succeed fast (since there is nothing to do).
      
      This is harmful as this create a false sense of "the series is passing" and
      Gitlab will use this simplistic pipeline for validation.
      
      By explicitly preventing the pipeline to be created in the merge-request case,
      we prevent this situation to happens
      
      Note that the job will be dropped (alonside phabricator) in the next two weeks
      anyway.
      477b5145e1a0
  14. May 12, 2022
  15. Apr 21, 2022
    • Martin von Zweigbergk's avatar
      rust-repo: make `Send` by not storing functions in `LazyCell` · 90a15199cbc6
      Martin von Zweigbergk authored
      We (Google) want to use `Repo` in a context where we can store it in
      `Mutex<Repo>`. However, that currently doesn't work because it's not
      `Send` because the `LazyCell` initialization functions are not
      `Send`. It's easy to fix that by passing them to the `get_or_init()`
      and `get_mut_or_init()` functions. We'll probably also want `Repo` to
      be `Send` (and even `Sync`) in core later, so this seems like a step
      in the right direction.
      
      Differential Revision: https://phab.mercurial-scm.org/D12582
      90a15199cbc6
  16. May 05, 2022
  17. May 04, 2022
  18. Apr 22, 2022
  19. May 02, 2022
    • Anton Shestakov's avatar
      followlines: don't put Unicode directly into the .js file (issue6559) · 2c0570a6d5ae
      Anton Shestakov authored
      Apparently some web server setups may serve this file in a different encoding
      than UTF-8, and that results in visual garbage in the followlines button that
      renders for every line in a file. So instead of using this Unicode character in
      UTF-8 we can encode it as \u2212. Or, to be more explicit, we can use &minus;
      HTML entity, which resolves into exactly that character.
      
      Since now we're using innerHTML property to set the minus part of the button,
      let's use it to set the plus part as well (even though the plus sign was plain
      ASCII). A wise man once said "A foolish consistency is the hobgob... eh,
      whatever." Throw a brick at me if this makes things worse.
      
      Differential Revision: https://phab.mercurial-scm.org/D12597
      2c0570a6d5ae
  20. Apr 28, 2022
  21. Apr 27, 2022
  22. Apr 26, 2022
  23. May 04, 2022
Loading