From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
BERENDSEN Arnoud <arnoud.berendsen@soprasteria.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Cleaning up "contrib/"
Date: Tue, 6 May 2025 07:40:39 +0200 [thread overview]
Message-ID: <aBmg1_wlF2fuk96M@pks.im> (raw)
In-Reply-To: <xmqq5xieq3fs.fsf@gitster.g>
On Mon, May 05, 2025 at 12:10:15PM -0700, Junio C Hamano wrote:
> Patrick Steinhardt <ps@pks.im> writes:
>
> > Many of the tools in "contrib/" fall into this category, and to the best
> > of my knowledge there isn't really a clear strategy for that directory.
> > So from my perspective, we should either rethink whether it is worth it
> > to have "contrib/" as part of Git, or we should at least do a spring
> > cleanup and drop bits that haven't seen any love in the last couple of
> > years.
>
> Things in contrib/ should either move up (to become a part of the
> core), move out (to become an independent project), or disappear.
So this very much sounds like staging drivers in the Linux kernel, where
[1] seems to match the description of yours. The only problem is that I
haven't really seen the described movement -- many of the pieces haven't
been touched for years.
I'll probably just send a patch series to get rid of at least a subset
of them. I also think that we should adapt the README and rephrase it
according to what the modern intention of this directory is, which seems
to have changed.
Other than that we also have some bits and pieces that _are_ actively
maintained, but that just don't have a better place to live:
- CMake.
- Coccinelle rules.
- Contacts.
- Credential helpers.
- Diff-highlight.
- git-jump.
- Shell completion.
Maybe they should be promoted and receive a proper home.
> But isn't git-svn not even part of contrib/?
Yeah, Dscho already corrected me.
Patrick
[1]: https://lwn.net/Articles/324279/
next prev parent reply other threads:[~2025-05-06 5:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 13:59 git svn clone failed BERENDSEN Arnoud
2025-05-04 8:19 ` Johannes Schindelin
2025-05-05 6:24 ` Cleaning up "contrib/" (was: git svn clone failed) Patrick Steinhardt
2025-05-05 7:36 ` Johannes Schindelin
2025-05-05 9:44 ` Patrick Steinhardt
2025-05-05 19:10 ` Cleaning up "contrib/" Junio C Hamano
2025-05-06 5:40 ` Patrick Steinhardt [this message]
2025-05-12 13:50 ` Jeff King
2025-05-13 0:13 ` brian m. carlson
2025-05-13 9:06 ` Patrick Steinhardt
2025-05-13 16:59 ` Junio C Hamano
2025-05-14 18:19 ` Jeff King
2025-05-14 20:05 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aBmg1_wlF2fuk96M@pks.im \
--to=ps@pks.im \
--cc=Johannes.Schindelin@gmx.de \
--cc=arnoud.berendsen@soprasteria.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).