Has anyone ever given consideration to git supporting a plugin architecture for git extensions? The idea would be to provide a consistent way to install, and address extensions to the core git functionality in a manner that does not require the extension to actually be integrated into the git core. For example, I have recently proposed a new command 'git work' https://github.com/jonseymour/git/blob/master/README.md which I think is a really useful extension to git. I haven't had much feedback for the concept. I am not sure if it is because people are too busy, just don't grok it, or grok it and don't think it is useful. So, perhaps it won't be included in git. That's fine, I can build my own fork of git which includes the proposed extension [ indeed, this is how I originally developed it]. That's fine for me, but it isn't the most practical way to distribute it to others since I'll have to produce distribution packages for a variety of different distribution formats or fallback to tars and zips. What would be call is if I could package my extension in a standard way and then anyone who was interested could simply do something like: git plugin install gitwork and then start using the commands as if they had built my fork of git themselves. jon. -- 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