On Saturday 06 September 2008 17:07, Steven Walter wrote: > After starting yap several weeks ago If you're interested in cross-platformness, you might want to be aware that there is already at least another 'yap' in Windows: MikTeX's DVI viewer (Yet Another Previewer). Just FYI. > By leveraging the extensible nature of yap, its svn mode strives to make > a remote svn repository act and feel as much like a git repository as > possible to lessen the impedance mismatch to the user. > * SVN interoperation > * Cloning an SVN repository is no different than cloning a git > repository (only slower) > * Same command to push to an SVN repo as a git repo > * Standard workflow (yap update) is appropriate for svn-based and > git-native setups > * Working with "cache repositories" is supported directly. When > cloning a repository generated by "yap clone <svn url>", the new > repositories is automatically configured to push back to the > subversion repository. This is an extremely interesting idea. I've always wondered myself if it were possible to make git-svn operation more transparent, although it has always been my understanding that the interface difference might be substantially driven by robustness, especially for 'roundtrip' operation, and by the fact that svn would not really be suited for some of the operations that are common in git workflow. It'll be interesting to see the level of transparency that can be achieved without bringing down the svn server ;) I think that the most complex situations arise from cloning svn repositories that undergo heavy structure changes in their history, moving from a structure where there was no trunk/branches/tags because the project was just kept in the svn root, to thetraditional trunk/branches/tags structure (I've come across at least two svn repositories like this in the past, and git-svn used to have quite some problems in importing them directely, although I haven't tried it recently). -- Giuseppe "Oblomov" Bilotta -- 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
