Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: > [1] git-svn.perl is a work of art and a wonder to behold, and if your aim > is to make a compatible replacement for it, the first step will be to > understand its design deeply. And the thing is, that much, while > valuable anyway, is pretty hard already. Thanks. I credit the use of automated tests for making things work as well as it does, especially given how ugly the code has gotten. I think the first step to understanding much of it is to split the modules into individual files and then understanding the test cases. > and people rely a lot on an odd coincidence: > > - using "git svn clone" twice with the same configuration on the same > repository will, at least most of the time, give the same commit > names. I did design that in mind when I first started, I'm glad it still mostly works after all this time :) > That is the dream. *My* dream was to replace Subversion and get people using git. git-svn was designed to be self-obsoleting from the start. For the most part I consider it a success since I no longer need to use it :) -- Eric Wong -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html