greened@xxxxxxxxxxxxx writes: > Junio, is there a policy for backward-compatability in contrib? I hope > that since that directory is for stuff not yet in mainline, there is > some room to massage the user interface. I do not think there is anything more than "we wish there were fewer such end-user facing changes." The purpose of having anything in contrib/ is to give them a way to gain more visibility than they otherwise would as standalone projects on their own. I don't want to control the day-to-day quality issues in them. That is what we have "guilty parties" for contrib/ subdirectories for, so that they can decide how mature their pieces in contrib/ are and what kind of b/c break is acceptable ;-) Thanks. -- 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