Skip to content
Snippets Groups Projects
  1. Mar 03, 2022
  2. Dec 24, 2021
    • Dan Villiom Podlaski Christiansen's avatar
      versioning: create branch 1.0.x · 08347725
      Dan Villiom Podlaski Christiansen authored
      The upcoming release will be called 1.0 rather than 0.11.0. The main
      motivation for this is that I consider hg-git “ready”. In order for
      semantic versioning to make sense, something has to eventually be good
      enough. With the changes to user experience, I personally consider
      this good enough to actually use. And besides, if this isn't 1.0, when
      should it be? When development ceases?
      
      I've updated `CONTRIBUTING.rst` to specify an explicit compatibility
      policy.
      08347725
  3. Jan 26, 2022
  4. Jan 21, 2022
  5. Dec 31, 2021
  6. Dec 27, 2021
  7. Dec 23, 2021
  8. Dec 30, 2021
  9. Nov 22, 2021
  10. Dec 23, 2021
  11. Dec 22, 2021
  12. Dec 17, 2021
  13. Nov 24, 2021
    • Dan Villiom Podlaski Christiansen's avatar
      pull: properly distinguish remote messages from progress · 77ce9797
      Dan Villiom Podlaski Christiansen authored
      The previous logic was kind of weird. It parsed the messages rather
      thoroughly, but ignored a crucial distinction:
      
      * Anything that ends with a newline is most likely a remote message.
      * Anything that ends with a carriage return is most likely a progress
        message.
      * Lines ending with newline always flush a progress session.
      
      Most things ending with newline are interesting, but we explicitly
      disregard the “totals” stuff. Things ending with carriage return are
      either progress, or at least something we shouldn't print.
      77ce9797
  14. Dec 02, 2021
  15. Jul 09, 2021
  16. May 03, 2021
  17. Nov 16, 2021
  18. Jun 21, 2021
  19. Jun 22, 2021
  20. Nov 05, 2021
    • Dan Villiom Podlaski Christiansen's avatar
      pull: ensure that all commits are at least draft · b7843bf6
      Dan Villiom Podlaski Christiansen authored
      Previously, setting phases.new-commit to `secret` would trigger an
      error in clone:
      
        abort: filtered revision '7fe02317c63d9ee324d4b5df7c9296085162da1b'
      
      I'm not entirely sure why that happens, I didn't delve too deeply.
      Essentially, pulls from hg-git _should_ be draft, so I fixed that
      instead. The `secret` phase is for stuff neither to push to Mercurial
      nor Git; it does not distinguish commits based on their origin.
      
      The bug report dates from several years ago; so long ago that one
      might reasonably debate whether this is a bug fix or an enhancement.
      Since fixing old code is significantly easier on default, that's where
      I've put this change.
      
      This is only a partial fix, that focuses on the bug specifically; it
      doesn't address edge-cases where a pull might only affect phases. For
      clarity and documentation, I've left the incorrect behaviour in the
      tests.
      
      Fixes #266
      b7843bf6
  21. May 31, 2021
  22. Jul 06, 2021
    • Dan Villiom Podlaski Christiansen's avatar
      push: output when non-pushable commits exist · 5b271ae3
      Dan Villiom Podlaski Christiansen authored
      This is an area where we have no choice but diverging from stock
      Mercurial, as Git does not allow anonymous heads. We can only push
      something that has either a bookmark or a tag.
      
      In order to lessen confusion for users, we output a message inspired
      by Mercurial's (ignoring %d secret commits) — which serves a similar
      purpose.
      5b271ae3
  23. Nov 03, 2021
  24. Jul 09, 2021
  25. Feb 05, 2021
  26. Oct 31, 2021
Loading