From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Ayman Bagabas via GitGitGadget" <gitgitgadget@gmail.com>,
git@vger.kernel.org, "Elijah Newren" <newren@gmail.com>,
"Taylor Blau" <me@ttaylorr.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Chris Torek" <chris.torek@gmail.com>,
"Ayman Bagabas" <ayman.bagabas@gmail.com>
Subject: Re: [PATCH v3] shell: allow overriding built-in commands
Date: Sun, 23 Mar 2025 22:27:32 -0700 [thread overview]
Message-ID: <xmqqy0wvov5n.fsf@gitster.g> (raw)
In-Reply-To: <20250324032550.GA690093@coredump.intra.peff.net> (Jeff King's message of "Sun, 23 Mar 2025 23:25:50 -0400")
Jeff King <peff@peff.net> writes:
> So it seems like a reasonable goal. A more restricted approach might be
> to provide a more formal hook/plugin interface. E.g., to run a hook
> script with the command name and arguments, and have it return
> success/failure to allow the to proceed.
>
> That's not quite as flexible (in your approach I could replace what
> upload-pack is doing entirely, cache its output, and so on). But it
> might be harder for admins to screw up. I dunno.
Yeah, we usually try not to be overly flexible for that reason, but
given that "git shell" is so limited that rewriting its services
wholesale is not all that much of a deal, I think it is OK.
I however wonder if it is worth admins' time and effort to add
features to "git-shell" using this new facility, or if they are
better off using something more established like gitolite once they
want to go fancier beyond what the basic "git-shell" offers.
next prev parent reply other threads:[~2025-03-24 5:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 10:01 [PATCH] [RFC] shell: allow overriding built-in commands Ayman Bagabas via GitGitGadget
2025-03-22 17:39 ` Elijah Newren
2025-03-22 18:02 ` Ayman Bagabas
2025-03-22 18:26 ` Elijah Newren
2025-03-23 0:12 ` [PATCH v2] " Ayman Bagabas via GitGitGadget
2025-03-23 1:11 ` Chris Torek
2025-03-23 15:05 ` Ayman Bagabas
2025-03-23 15:12 ` Chris Torek
2025-03-23 15:29 ` [PATCH v3] " Ayman Bagabas via GitGitGadget
2025-03-24 3:25 ` Jeff King
2025-03-24 5:27 ` Junio C Hamano [this message]
2025-03-24 20:28 ` Jeff King
2025-03-25 22:44 ` Ayman Bagabas
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=xmqqy0wvov5n.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=ayman.bagabas@gmail.com \
--cc=chris.torek@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=me@ttaylorr.com \
--cc=newren@gmail.com \
--cc=peff@peff.net \
/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).