From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Chris Maes <chris.maes@macq.eu>
Cc: philipp@gortan.org, avarab@gmail.com, git@vger.kernel.org,
philipoakley@iee.org
Subject: Re: git-gui ignores core.hooksPath
Date: Wed, 11 Apr 2018 00:06:24 +0200 (DST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1804110001350.56@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz> (raw)
In-Reply-To: <3a3eb88e-0d7b-e689-c4e4-207569ebd667@macq.eu>
Hi Chris,
On Tue, 10 Apr 2018, Chris Maes wrote:
> using git 2.16 the same problem is still present.
And probably 2.17, too.
> I see that the pull request https://github.com/patthoyts/git-gui/pull/12
> (along with 15 other pull requests) are lying around since about one
> year without any sign of life from patthoyts.
Yes, this is very sad. I hope he is alive and doing well.
As to Git GUI: if you know your way around Tcl/Tk reasonably well, how
about stepping up and reviewing those PRs? Even if the PRs are not merged,
a review would do those PRs pretty good and we could then take things from
there.
> 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?
There is no "assigning" here, not really. What is missing is a volunteer
who earned the trust of the Git developers. Reviewing those PRs would go a
long way to earn that trust.
> Just hoping to revive the discussion here, since the
> https://github.com/patthoyts/git-gui/ repository seems quite dead.
Thank you for doing this.
I also hope that somebody with reasonable understanding of Tcl/Tk and a
vested interest in Git GUI takes up the responsibility of maintaining it.
Judging by the rate the PRs trickled into
https://github.com/patthoyts/git-gui, I think it would be a minor time
commitment.
Ciao,
Johannes
next prev parent reply other threads:[~2018-04-10 22:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 13:41 git-gui ignores core.hooksPath Philipp Gortan
2017-06-02 14:21 ` Samuel Lijin
2017-06-02 16:38 ` Ævar Arnfjörð Bjarmason
2017-06-02 20:23 ` [PATCH] respect core.hooksPath, falling back to .git/hooks Philipp Gortan
2017-06-02 20:39 ` Philipp Gortan
2017-06-14 13:24 ` Johannes Schindelin
2017-06-02 23:00 ` git-gui ignores core.hooksPath Philip Oakley
2017-06-02 23:21 ` Philipp Gortan
2017-06-14 13:15 ` Johannes Schindelin
2017-06-14 13:25 ` Philipp Gortan
2018-04-10 15:00 ` Chris Maes
2018-04-10 22:06 ` Johannes Schindelin [this message]
2018-04-10 22:50 ` Junio C Hamano
2018-04-10 23:31 ` Ævar Arnfjörð Bjarmason
2018-04-11 0:44 ` Junio C Hamano
2018-06-05 5:48 ` Bert Wesarg
2018-06-11 21:58 ` Stefan Beller
2018-06-12 6:09 ` Johannes Sixt
2018-07-10 12:08 ` Johannes Schindelin
2018-07-10 15:18 ` Philip Oakley
-- strict thread matches above, loose matches on Subject: below --
2017-02-04 17:14 git-gui ignores core.hookspath matthias.serfling
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1804110001350.56@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz \
--to=johannes.schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=chris.maes@macq.eu \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.org \
--cc=philipp@gortan.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).