public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Junio C Hamano <gitster@pobox•com>
To: Paul Mackerras <paulus@ozlabs•org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx•de>,
	 Beat Bolli <dev+git@drbeat•li>,
	 Tobias Pietzsch via GitGitGadget <gitgitgadget@gmail•com>,
	 git@vger•kernel.org,
	 Tobias Pietzsch <tobias.pietzsch@gmail•com>
Subject: Re: The health of gitk, was Re: [PATCH] gitk: check main window visibility before waiting for it to show
Date: Thu, 14 Nov 2024 17:07:18 +0900	[thread overview]
Message-ID: <xmqqed3e6xxl.fsf@gitster.g> (raw)
In-Reply-To: <ZzWkgblaoWehC0kY@thinks.paulus.ozlabs.org> (Paul Mackerras's message of "Thu, 14 Nov 2024 18:19:29 +1100")

Paul Mackerras <paulus@ozlabs•org> writes:

> I recently (as in several weeks ago) sent Junio Hamano an email asking
> this question, and asking for his opinion on the best way to proceed
> with gitk patches, but got no reply.

Ah, it was probably (just) before I took a few weeks off, and I
completely forgot about it.  I tried to be careful pushing back
patches that touch both inside and outside gitk but I wouldn't be
surprised if some slipped in by mistake.  We could split them out
and get your tree back in sync, if you prefer to keep gitk as
semi-independent project that is subtree bound to our tree.  The
arrangement had merit in early days, back when git itself and gitk
could have different release cadence, but in practice, I haven't
seen gitk separately issuing freestanding releases to end users (or
end-users installing versions of gitk independent from the version
of git they have, for that matter), so perhaps the separate tree
arrangement has outlived its usefulness?  I dunno.

Thanks.

next prev parent reply	other threads:[~2024-11-14  8:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-09 23:26 [PATCH] gitk: check main window visibility before waiting for it to show Tobias Pietzsch via GitGitGadget
2021-01-10 22:23 ` Beat Bolli
     [not found]   ` <ddee92a7-3d1e-f869-9cc4-72b70eee0dd5@gmx.de>
2024-11-13  7:47     ` The health of gitk, was " Johannes Schindelin
2024-11-14  7:19     ` Paul Mackerras
2024-11-14  8:07       ` Junio C Hamano [this message]
2024-11-17 15:26       ` Gitk maintainership, was Re: The health of gitk Johannes Sixt
2024-11-19  9:59         ` Paul Mackerras
2024-11-19 18:49           ` Johannes Sixt

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqed3e6xxl.fsf@gitster.g \
    --to=gitster@pobox$(echo .)com \
    --cc=Johannes.Schindelin@gmx$(echo .)de \
    --cc=dev+git@drbeat$(echo .)li \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitgitgadget@gmail$(echo .)com \
    --cc=paulus@ozlabs$(echo .)org \
    --cc=tobias.pietzsch@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox