From: Junio C Hamano <email@example.com>
To: Pratyush Yadav <firstname.lastname@example.org>,
Pat Thoyts <email@example.com>
Cc: firstname.lastname@example.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] git-gui: Call do_quit before destroying the main window
Date: Fri, 09 Aug 2019 13:03:12 -0700 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Pratyush Yadav's message of "Fri, 9 Aug 2019 20:12:33 +0530")
Pratyush Yadav <email@example.com> writes:
>> If you meant to volunteer to act as a git-gui maintainer, that would
>> be wonderful. Then I do not have to play an interim maintainer.
> Yes, I do mean to volunteer to act as a git-gui maintainer.
> Is there something I should know other than
Well, I do not think that document has anything useful for being a
maintainer for git-gui in it.
The Git community members needs to be able to trust that the new
Git-gui maintainer would make a sensible decision when picking up
(or asking to improve) a patch from the list to collect and forward
to me. We somehow need to make sure that happens.
It also is nice if we can get the handing over the maintainership
endorsed by the current Git-gui maintainer.
Compared to that, the procedural issues (how the patches are
reviewed, when and how they are forwarded to me, etc.) are much less
next prev parent reply other threads:[~2019-08-09 20:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 14:39 [PATCH] git-gui: Call do_quit before destroying the main window Pratyush Yadav
2019-08-06 15:52 ` Pratyush Yadav
2019-08-06 18:22 ` Junio C Hamano
2019-08-06 19:04 ` Pratyush Yadav
2019-08-07 5:21 ` Junio C Hamano
2019-08-07 17:41 ` Junio C Hamano
2019-08-07 17:50 ` Junio C Hamano
2019-08-07 21:03 ` Pratyush Yadav
2019-08-07 21:53 ` Junio C Hamano
2019-08-09 14:42 ` Pratyush Yadav
2019-08-09 20:03 ` Junio C Hamano [this message]
2019-08-13 13:40 ` Pratyush Yadav
2019-08-13 17:30 ` Junio C Hamano
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:
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 \
* 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
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).