> > It is serious. > > The purpose of the 'contrib/' area is not clear. The statemens coming > from Junio don't match what is on 'contrib/README'. So we have a huge > variance of quality all over 'contrib/'. Some tools in contrib have > higher quality than what is part of the core (e.g. they have tests, > while git-archimport doesn't).
How about rewriting the README then? Also as I said in another mail, we could split up the contrib/ area into multiple areas with narrow defined use-cases, i.e. staging/, Documentation/historicTools (the current contrib/examples section), 3rdPartyTools/, Bridges/ (for cooperating with other VCS). > > So this is a serious attempt at making sure we remain consistent through > the core and contrib/. > > Personally I would like to see everything in contrib/ have *at least* > some tests and documentation. Otherwise we know what's going to happen; > they are going to rot and nobody will care that the tools don't work any > more, or they won't even know what they do and how to use them. > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
