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

The fundamental problem is that git doesn't track branches in any sane way. Maybe it would be better to fix that? Fossil remembers what branch a commit was committed on, so the task branch itself is a change ID. That might be tricky to solve while also allowing git commands to mess with history of course. Fossil doesn't have that problem.


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

Search: