| commit | 49eb8d39c78f161231e63293df60f343d208f409 | |
| author | Ævar Arnfjörð Bjarmason <avarab@gmail.com> | |
| Sun, 25 Mar 2018 20:46:53 +0000 (25 20:46 +0000) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 26 Mar 2018 20:48:50 +0000 (26 13:48 -0700) | ||
| tree | 877abb15a47d8f0185fffa0103f78a66382a02e9 | treesnapshot (tar.gz zip) |
| parent | 90bbd502d54fe920356fa9278055dc9c9bfe9a56 | commitdiff |
Remove contrib/examples/*
There were some side discussions at Git Merge this year about how we
should just update the README to tell users they can dig these up from
the history if the need them, do that.
Looking at the "git log" for this directory we get quite a bit more
patch churn than we should here, mainly from things fixing various
tree-wide issues.
There's also confusion on the list occasionally about how these should
be treated, "Re: [PATCH 1/4] stash: convert apply to
builtin" (<CA+CzEk9QpmHK_TSBwQfEedNqrcVSBp3xY7bdv1YA_KxePiFeXw@mail.gmail.com>)
being the latest example of that.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
There were some side discussions at Git Merge this year about how we
should just update the README to tell users they can dig these up from
the history if the need them, do that.
Looking at the "git log" for this directory we get quite a bit more
patch churn than we should here, mainly from things fixing various
tree-wide issues.
There's also confusion on the list occasionally about how these should
be treated, "Re: [PATCH 1/4] stash: convert apply to
builtin" (<CA+CzEk9QpmHK_TSBwQfEedNqrcVSBp3xY7bdv1YA_KxePiFeXw@mail.gmail.com>)
being the latest example of that.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
27 files changed: