Skip to content
Snippets Groups Projects
  1. Apr 05, 2022
  2. Mar 22, 2022
  3. Apr 05, 2022
  4. May 02, 2022
  5. May 19, 2022
  6. May 16, 2022
    • Pierre-Yves David's avatar
      fix-ci: backed out changeset 308e45f7b455 · 22279b60
      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.
      22279b60
  7. May 12, 2022
    • Kyle Lippincott's avatar
      amend: stop specifying matcher, get all copies in wctx · df68d64b
      Kyle Lippincott authored
      When we're recreating the commit that we'll be committing, we don't want to
      filter our copy information based on just the *new* [versions of the] files
      we're amending. The test has an example of this case, but for clarity, the
      situation is:
      
      ```
      $ hg cp src dst && hg commit
      <do some work>
      $ hg amend some_unrelated_file.txt
      $ hg status --copies
      A dst
      A some_unrelated_file.txt
      ```
      
      What *should* happen is that `dst` should remain marked as a copy of `src`, but
      this did not previously happen. `matcher` here only includes the files that were
      specified on the commandline, so it only gets the copy information (if any, in
      this example there's not) for `some_unrelated_file.txt`. When it goes to apply
      the memctx to actually create the commit, the file copy information is
      incomplete and loses the information for the files that shouldn't have been
      affected at all by the amend.
      
      Differential Revision: https://phab.mercurial-scm.org/D12625
      df68d64b
    • Kyle Lippincott's avatar
  8. May 05, 2022
  9. May 04, 2022
  10. Apr 22, 2022
  11. Apr 27, 2022
  12. Apr 26, 2022
  13. May 04, 2022
  14. Apr 28, 2022
  15. Apr 25, 2022
  16. Apr 19, 2022
    • Raphaël Gomès's avatar
      rhg: use `Command::exec` instead of `Command::status` · 006688e3
      Raphaël Gomès authored
      `rhg` is supposed to be a transparent executable, using a subprocess defeats
      that purpose. See inline comments for more details.
      
      This also introduces the `which` crate to check if the fallback executable
      actually exists to help debugging (plain `execve` doesn't give much
      information).
      
      The error code 253 is used to signify that the fallback is not found, but may
      mean in the future that it is otherwise invalid if we start being more
      specific.
      
      Differential Revision: https://phab.mercurial-scm.org/D12578
      006688e3
  17. Apr 27, 2022
  18. Apr 19, 2022
  19. Apr 13, 2022
  20. Apr 12, 2022
  21. Apr 19, 2022
  22. Apr 13, 2022
  23. Apr 09, 2022
  24. Apr 11, 2022
Loading