Charles Duffy wrote: > Sean wrote: >> You'll need a better example than that. Git has supported a version >> of Cygwin-compatible symlink support on Windows for quite some time. >> And no plugins were needed. > > The win32-compatible symlink support is not, in and of itself, the point. > > The point is that core, pervasive functionality can be modified at > runtime, with no recompilation or installation of tools not included in > the bzr package itself, simply by dropping a directory into place. This > means that folks who don't have the skillset to merge three branches > together (say, upstream plus two different trees adding extra > functionality) and run a build can still install a few plugins to > enhance their copy of bzr (which was installed by their IT staff, or a > shiny click-through idiot-friendly Windows installer, etc). You don't need plugins for that. Take for example git-svn (perhaps not the best example, as it is Perl script; but Python although has compiled form is script language at heart), which went AFAIK from external contribution, to being in contrib/, to being in mainline (and in git-svn package). About plugins modifying some core functionality: this is rather sign of not attracting developers to do it in-core... -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - 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