Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

As sibling mentioned, this is totally solved by git-rerere.


Partially. Unfortunatly, rerere is not perfect, and will only solve 80% of the cases.

For big rebase, this can add up to a lot, which I just paid the price last week.


When can we move to Sapling again?


How would Sapling avoid this? As I understand it it uses the same data model as Mercurial which is really the same as Git's. I think you would need something like Pijul to solve it nicely. At least as far as I can tell.

I might actually try this in Pijul because I too encounter this semi-regularly (it's not a freak occurrence at all) and my solution is basically to give up and squash my branch before rebasing.


I already have - it’s pretty great :D




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: