From: Pratyush Yadav <firstname.lastname@example.org> To: Junio C Hamano <email@example.com> Cc: Pat Thoyts <firstname.lastname@example.org>, email@example.com, Johannes Schindelin <Johannes.Schindelin@gmx.de> Subject: Re: [PATCH] git-gui: Call do_quit before destroying the main window Date: Tue, 13 Aug 2019 19:10:43 +0530 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On 09/08/19 01:03PM, Junio C Hamano wrote: > Pratyush Yadav <firstname.lastname@example.org> 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 > > Documentation/howto/maintain-git.txt? > > 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. Yes, but how? Of course, I don't intend to run this thing into the ground. I want the project to be useful for everyone. I only recently got involved with the project, and so most people here don't know me or my work that well. Maybe me contributing to the main git project can help. But other than that, the only way to build that trust is with time. > It also is nice if we can get the handing over the maintainership > endorsed by the current Git-gui maintainer. Well, Pat has not replied to your email, so I don't think that will be possible. > Compared to that, the procedural issues (how the patches are > reviewed, when and how they are forwarded to me, etc.) are much less > important. Of course. But knowing them doesn't hurt :).  https://public-inbox.org/git/CAP8UFD1C_FD5TLz0oyn6QzGU2rdvvTe6PNhpK29vkMfuHimemail@example.com/ -- Regards, Pratyush Yadav
next prev parent reply other threads:[~2019-08-13 13:40 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-04 14:39 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 2019-08-13 13:40 ` Pratyush Yadav [this message] 2019-08-13 17:30 ` 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 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 \ --firstname.lastname@example.org \ --email@example.com \ --cc=Johannes.Schindelin@gmx.de \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] git-gui: Call do_quit before destroying the main window' \ /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
Code repositories for project(s) associated with this 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).