From: Junio C Hamano <email@example.com> To: Pratyush Yadav <firstname.lastname@example.org> Cc: email@example.com, Johannes Schindelin <Johannes.Schindelin@gmx.de> Subject: Re: [PATCH] git-gui: Call do_quit before destroying the main window Date: Tue, 06 Aug 2019 22:21:17 -0700 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> (Pratyush Yadav's message of "Wed, 7 Aug 2019 00:34:51 +0530") Pratyush Yadav <firstname.lastname@example.org> writes: > I'm not too optimistic on finding someone to run this project. I asked > on the list who the maintainer is , and no one came up. The repo at >  also seems abandoned. In the meantime until somebody steps up, I might run my own copy. I need to allocate a block of time to see how stale Pat's tree is (e.g. its mainline may have more commits than what we have pulled, in which case we need to be extra careful---these old commits may be something Pat found dubious and decided to wait before telling me to pull, and we would be better off ignoring them) before I can say anything definite, but I am hoping that there won't be too many patches flowing to the git-gui project; anything high volume and/or tricky tcl/tk would be beyond my capacity as an interim maintainer to maintain the quality of the codebase of it.
next prev parent reply other threads:[~2019-08-07 5:21 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 [this message] 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 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 \ --email@example.com \ --firstname.lastname@example.org \ --cc=Johannes.Schindelin@gmx.de \ --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).