Re: git-gui ignores core.hooksPath

From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Apr 10, 2018, 23:31 UTC
Message-ID: <87muyabpuz.fsf@evledraar.gmail.com>
In-Reply-To: <xmqqd0z61xsv.fsf@gitster-ct.c.googlers.com>

On Tue, Apr 10 2018, Junio C. Hamano wrote:

Show 21 quoted lines

> Chris Maes <chris.maes@macq.eu> writes:
>
>> Is there any hope from here that anyone will pick up this / these
>> changes? Will anyone else be assigned the main responsible for this
>> git-gui repository?
>>
>> Just hoping to revive the discussion here, since the
>> https://github.com/patthoyts/git-gui/ repository seems quite dead.
>
> It indeed does.
>
> I've played a patch-monkey in the past for git-gui and have a few
> topics queued still in my tree, but that serves merely as a bookmark
> that is slightly better than a pointer to the mailing list archive.
>
> We need a volunteer to take over this part of the subsystem;
> somebody who actually uses it, passionate about improving it, and
> can speak tcl/tk somewhat fluently (I qualify none of these three
> criteria myself).
>
> Any takers?

Isn't everyone involved much better solved if we come up with some plan to split these off from git.git? I.e. I think if if git-gui, gitk and gitweb were proposed for inclusion in-tree today I don't think we'd bite, and instead point to things like [1] or [2].

Of the three gitweb is a bit more glued to the rest of the codebase (test & custom test lib), but gitk and git-gui already have their own external projects.

It looks like if they started making tagged releases, along with some small Makefile changes like generating their manpages from ASCIIDOC, downstream packagers of git-gui and gitk could simply start pointing to those as the authoritative source instead of whatever gets shipped with git.

1. https://git-scm.com/downloads/guis/
2. https://git.wiki.kernel.org/index.php/Interfaces,_frontends,_and_tools#Web_Interfaces