From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
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: Mon, 05 May 2025 12:10:15 -0700 [thread overview]
Message-ID: <xmqq5xieq3fs.fsf@gitster.g> (raw)
In-Reply-To: <aBhZHA7av8bWH9Ac@pks.im> (Patrick Steinhardt's message of "Mon, 5 May 2025 08:24:34 +0200")
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.
But isn't git-svn not even part of contrib/?
next prev parent reply other threads:[~2025-05-05 19:10 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 ` Junio C Hamano [this message]
2025-05-06 5:40 ` Cleaning up "contrib/" Patrick Steinhardt
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=xmqq5xieq3fs.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=arnoud.berendsen@soprasteria.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.