On 29.11.2009, at 08:50, Daniele Segato wrote: > You had to understand the difference between a distributed version > control system (git) and a centralized version control system (svn). I understand that, I use (pure) git for all my personal projects, and it works great. And even as a front end for SVN, I am *very* happy with what I got from git-svn so far, I think it is an excellent tool, even better than the actual SVN client. I track an SVN repository in my local git master branch, then branch off locally for development, send patches for review, reorder/consolidate/squash commits back onto my master branch and then dcommit that back to SVN. All that is great. I would like to understand why git svn clone -r n <url> does not work as expected while git svn clone -r m <url> does work perfectly fine, if that m revision number happens to have been committed on the particular SVN branch I cloned (you left off that -r in your git svn clone examples). As it is, I have to hunt for the next lower or higher revision number that happens to be on that branch. I might be doing a poor job explaining what my question is... Basically, what prevents that operation from doing the same thing that SVN does? Lack of information, i.e. should I just clone higher up in the tree? ______________________________ Marc Liyanage www.entropy.ch skype mliyanage iChat liyanage@xxxxxxx -- 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