Re: [PATCH v1 19/25] contrib: remove 'diff-highlight'

From: Stefan Beller <stefanbeller@gmail.com>
Date: May 9, 2014, 13:37 UTC
Message-ID: <CALbm-EbcoZmWtuxMLSZWjPcgKVTXZPcQ_ppj2UGKzF9oh+hQvA@mail.gmail.com>
In-Reply-To: <536c35a3507a8_741a161d310cf@nysa.notmuch>

Show 8 quoted lines

>
> 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).

Show 9 quoted lines

>
> 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.
>