From: Johannes Schindelin <Johannes.Schindelin@gmx•de>
To: Patrick Steinhardt <ps@pks•im>
Cc: BERENDSEN Arnoud <arnoud.berendsen@soprasteria•com>,
"git@vger•kernel.org" <git@vger•kernel.org>
Subject: Re: Cleaning up "contrib/" (was: git svn clone failed)
Date: Mon, 5 May 2025 09:36:06 +0200 (CEST) [thread overview]
Message-ID: <5ffefc29-75ee-e278-448c-9124740d02fb@gmx.de> (raw)
In-Reply-To: <aBhZHA7av8bWH9Ac@pks.im>
Hi Patrick,
On Mon, 5 May 2025, Patrick Steinhardt wrote:
> On Sun, May 04, 2025 at 10:19:06AM +0200, Johannes Schindelin wrote:
> >
> > On Fri, 2 May 2025, BERENDSEN Arnoud wrote:
> >
> > > [... talks about `git svn` not working in Git for Windows ...]
> >
> > In Git for Windows, `git svn` is quite a maintenance burden [... then
> > suggests to use Windows System for Linux (WSL) as a workaround ...].
>
> I sometimes wonder whether we should move such basically-unmaintained
> scripts out of the Git repository. They do a disservice to both us and
> to our users as they create the wrong impression of being the sanctioned
> way of doing a particular task even though they have only been gathering
> dust for ages.
>
> 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.
While I am thoroughly sympathetic to the idea of cleaning up `contrib/`
(which is a mixture of things that are quite well supported, such as the
Bash tab completion script, and of things that are the opposite of
maintained, such as `contrib/workdir/` that should have been dropped a
long time ago since it encourages relying on Git's internals and has been
superseded by `git worktree`), I cannot fail to notice that `git-svn`
isn't even in `contrib/`.
Instead, `git-svn` is in the same category as `git-archimport`,
`git-cvsserver`, `git-cvsexportcommit` and `git-cvsimport`, i.e. Git
commands that tried to facilitate transitioning from specific version
control systems that had been a lot more common than Git at the time, but
no longer are. Maybe `git-svn` is not quite as obsolete as the other
commands in that category, but they are all merely dust collectors in
Git's codebase.
Ciao,
Johannes
next prev parent reply other threads:[~2025-05-05 7:36 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 [this message]
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
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=5ffefc29-75ee-e278-448c-9124740d02fb@gmx.de \
--to=johannes.schindelin@gmx$(echo .)de \
--cc=arnoud.berendsen@soprasteria$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=ps@pks$(echo .)im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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