3 ms·
hmm, am I the only who wishes that issues where simply files in a directory inside the repository? It seems crazy that when you fork an old version, you have n
by tomjen3 16y ago
hmm, am I the only who wishes that issues where simply files in a directory inside the repository?
It seems crazy that when you fork an old version, you have no idea which bugs have been fixed and if you later merge again you have to manually track down which bugs have been fixed.
- brendano 16y agoYou might be interested in: http://ditz.rubyforge.org/ http://ditz.rubyforge.org/
- roryokane 16y agoTicGit-ng looks like it solves this problem (I haven’t tried it): https://github.com/jeffWelling/ticgit https://github.com/jeffWelling/ticgit
- St-Clock 16y agoYou might also be interested in gitli (excellent for single-developer projects, good-enough for small teams): https://github.com/bartdag/gitli https://github.com/bartdag/gitli