This patch series introduces the concept of extra components. These are
components which are not yet part of the core but are good enough for
distributions to ship, and in fact, they already do.
This benefits everyone:
1. Distribution packagers that just want to do `make install`
2. People who download git's source code and just want to do
`make install`
3. Developers who have no idea what's production-level quality in
contrib/ and just want to do `make install`.
For now they'll have to do `make install install-extra`. But if the
result is deemed correct, we might choose to add "install-extra" to the
"install" target.
The measuring stick I'm using to gauge if a component in contrib belongs
in extra is simple: are we already running tests for them with
'make test'? If the answer is "yes, we do run tests", then the answer is
"yes, it belongs in contrib".
We might want to move more components from contrib to extra once their
tests are being run reliably.
And we might move some components from the core which aren't really part
of the core to extra, like gitk, git-gui, git-p4, and git-svn.
For now only part of contrib/completion is graduated to the new area.
Since v2 I removed workdir from the list of graduates as Philippe Blain
suggested.
Felipe Contreras (1):
completion: graduate out of contrib
Makefile | 10 ++++++++++
{contrib => extra}/completion/git-completion.bash | 0
{contrib => extra}/completion/git-completion.zsh | 0
{contrib => extra}/completion/git-prompt.sh | 0
t/t9902-completion.sh | 8 ++++----
t/t9903-bash-prompt.sh | 2 +-
6 files changed, 15 insertions(+), 5 deletions(-)
rename {contrib => extra}/completion/git-completion.bash (100%)
rename {contrib => extra}/completion/git-completion.zsh (100%)
rename {contrib => extra}/completion/git-prompt.sh (100%)
Range-diff against v2:
1: 3f44bc3253 = 1: 3f44bc3253 completion: graduate out of contrib
2: af9b24eeb1 < -: ---------- git-new-workdir: graduate out of contrib
--
2.32.0.38.g1d70fa854e
