From: "brian m. carlson" <sandals@crustytoothpaste•net>
To: Jeff King <peff@peff•net>
Cc: Patrick Steinhardt <ps@pks•im>,
Junio C Hamano <gitster@pobox•com>,
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, 13 May 2025 00:13:30 +0000 [thread overview]
Message-ID: <aCKOqs52TDZDvAXJ@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <20250512135017.GC1191957@coredump.intra.peff.net>
[-- Attachment #1: Type: text/plain, Size: 2769 bytes --]
On 2025-05-12 at 13:50:17, Jeff King wrote:
> On Tue, May 06, 2025 at 07:40:39AM +0200, Patrick Steinhardt wrote:
>
> > 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:
> >
> > [...]
> > - Diff-highlight.
> > - git-jump.
>
> These two are due to me. I don't have a problem moving them into their
> own projects if we want to clean out contrib.
>
> I think diff-highlight is something that _should_ eventually happen
> inside git-diff itself (because it would be more efficient and we could
> do a better job). But it wouldn't share any implementation with what's
> in contrib/.
I think there are definitely users of diff-highlight. I remember seeing
a reference to it recently and not realizing it was in contrib, but it
is actually used by others. I don't use it myself, though.
> > - Credential helpers.
>
> These ones are tricky. In theory they could be spun off into their own
> projects, and we already have examples in the wild of things like GCM
> which are maintained totally separately.
>
> But I think we may need to find people to step up as maintainers. In
> particular, I think osxkeychain is probably used by a lot of people, and
> probably shouldn't just go away. But I don't know how the maintainer
> would be. I wrote it originally, but don't (and never did) use it
> myself, or even have access to a macOS machine.
These are often shipped by distributors. Apple ships osxkeychain, as
does Homebrew. Many Linux distros ship libsecret and it's the
recommended choice for desktop Linux.
wincred, while not super popular, is still used and is smaller and
lighter than GCM. It doesn't actually look like GCM is seeing a great
deal of maintenance either at this point, so I'd say they're about
equally well maintained. Since I don't use Windows, I don't know if
there are other usecases (such as noninteractive uses) that are better
supported by wincred, but I'd recommend keeping it.
I definitely want us to keep these somewhere since they are quite
commonly used (even wincred) and getting rid of them will break a lot of
people and leave them without a secure credential storage option. We
could promote them to the main repository and simply build them with a
Makefile knob (or by default on the appropriate platform) and in CI, in
which case we'd at least know they build.
I'm not volunteering to be _the_ maintainer for libsecret, but I will
definitely contribute to making it work since I use it. This is much
like I am not _the_ maintainer for making Git work with Kerberos, but I
do certainly often fix it should it break.
--
brian m. carlson (they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 325 bytes --]
next prev parent reply other threads:[~2025-05-13 0:13 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
2025-05-12 13:50 ` Jeff King
2025-05-13 0:13 ` brian m. carlson [this message]
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=aCKOqs52TDZDvAXJ@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste$(echo .)net \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=arnoud.berendsen@soprasteria$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=peff@peff$(echo .)net \
--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