Skip to content

Releases: rhizoome/git-darcs

v0.7.5

06 Sep 07:46
Compare
Choose a tag to compare
  • wipe is only needed if we did renames
  • check if fast-forward is possible without merge

v0.7.4

05 Sep 09:20
Compare
Choose a tag to compare
  • fix cloning no-working-dir is not working

v0.7.3

05 Sep 08:32
Compare
Choose a tag to compare
  • only record the very first commit if no checkpoint is found

v0.7.2

04 Sep 22:28
Compare
Choose a tag to compare
  • actually do what we threaten: wipe the repo

v0.7.1

04 Sep 21:45
Compare
Choose a tag to compare
  • disable ancestry-path in oneline log

v0.7.0

04 Sep 21:25
Compare
Choose a tag to compare

ignoring merge-commits improves the results in two ways:

  • on some repositories git-darcs gets caught-up in merge-commits, recording almost only merges (I am testing with 6 repos I ofter work with)
    • in the problematic repos ignoring merges increases the amount of recorded patches by a order of magnitude
    • in repos with almost linear history ignoring merges has no effect on the amount of patches found
  • the history becomes more readable

v0.6.1

04 Sep 16:09
Compare
Choose a tag to compare
  • send documentation to pypi

v0.6.0

04 Sep 14:32
Compare
Choose a tag to compare
  • I found more correct way to linearize history. No more wrong rmfile or move in the wrong direction. But the new method skips more commits. There is always a downside. 🤘

v0.5.0

03 Sep 21:16
Compare
Choose a tag to compare
  • remove --no-merge, it can cause wrong result (better confusing, but not wrong)

v0.4.0

03 Sep 17:09
Compare
Choose a tag to compare
  • relax python versions to 3.8. 3.9 and 3.10