Follow-up Comment #2, bug #44993 (project avr-libc): Yes, Git makes some things different and after using it for a while one can learn it makes these things better. One can learn that merging is evil and rebasing is a godsend. Entirely different workflow.
Admittedly, that's not exactly obvious to people who are used to an unchangeable history and have nothing but merging at hand, so they've never seen the concept of topic branches at work. That said, avr-libc is very matured, so the number of experimental branches is low (zero?) and topic branches aren't urgent. To the bug opener: git-svn handles a Subversion repo just like a Git repo locally and works very well, so it's entirely fine for following avr-libc and also for preparing patches for it. Something like git svn clone http://svn.savannah.nongnu.org/svn/avr-libc should get you started. Initially it takes a while, but after that it's a fine tool. _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?44993> _______________________________________________ Nachricht gesendet von/durch Savannah http://savannah.nongnu.org/ _______________________________________________ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
