From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>
Subject: Re: [PATCH v2] doc/gitk: update reference to the external project
Date: Wed, 20 Aug 2025 08:34:25 -0700 [thread overview]
Message-ID: <xmqqv7miatxa.fsf@gitster.g> (raw)
In-Reply-To: <249056e7-1332-4e6f-8d07-16c80fd4913e@kdbg.org> (Johannes Sixt's message of "Wed, 20 Aug 2025 08:16:05 +0200")
Johannes Sixt <j6t@kdbg.org> writes:
> Gitk is now maintained by Johannes Sixt and the repository can be
> cloned from a new URL. b59358100c20 (Update the official repo of
> gitk, 2024-12-24) could have updated this instance in the manual,
> too, but the opportunity was missed. Update it now. Do give credit
> to Paul Mackerras as the inventor of the program.
>
> Signed-off-by: Johannes Sixt <j6t@kdbg.org>
> ---
Thanks for the update. This is long overdue. I forgot that this
manual page was carried in my tree.
> I just noticed that I would have removed the last user-visible
> mention of Paul. Don't do that.
>
> Documentation/gitk.adoc | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/gitk.adoc b/Documentation/gitk.adoc
> index 58ce40ddb1..5b34dcd077 100644
> --- a/Documentation/gitk.adoc
> +++ b/Documentation/gitk.adoc
> @@ -163,16 +163,16 @@ used by default. If '$XDG_CONFIG_HOME' is not set it defaults to
>
> History
> -------
> -Gitk was the first graphical repository browser. It's written in
> -tcl/tk.
> +Gitk was the first graphical repository browser, written by
> +Paul Mackerras in Tcl/Tk.
>
> 'gitk' is actually maintained as an independent project, but stable
> versions are distributed as part of the Git suite for the convenience
> of end users.
>
> -gitk-git/ comes from Paul Mackerras's gitk project:
> +`gitk-git/` comes from Johannes Sixt's gitk project:
>
> - git://ozlabs.org/~paulus/gitk
> + https://github.com/j6t/gitk
>
> SEE ALSO
> --------
next prev parent reply other threads:[~2025-08-20 15:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 8:18 [PATCH 0/3] meson: wire up gitk and git-gui Patrick Steinhardt
2025-08-19 8:18 ` [PATCH 1/3] git-gui: move into "subprojects/" Patrick Steinhardt
2025-08-19 9:36 ` Karthik Nayak
2025-08-19 8:18 ` [PATCH 2/3] gitk: " Patrick Steinhardt
2025-08-20 5:49 ` [PATCH] doc/gitk: update reference to the external project Johannes Sixt
2025-08-20 6:16 ` [PATCH v2] " Johannes Sixt
2025-08-20 15:34 ` Junio C Hamano [this message]
2025-08-19 8:18 ` [PATCH 3/3] meson: wire up gitk and git-gui Patrick Steinhardt
2025-08-19 9:40 ` Karthik Nayak
2025-08-24 17:25 ` Patrick Steinhardt
2025-08-19 15:49 ` [PATCH 0/3] " Junio C Hamano
2025-08-24 17:25 ` Patrick Steinhardt
2025-08-26 0:40 ` Junio C Hamano
2025-09-02 13:00 ` Patrick Steinhardt
2025-08-19 22:25 ` Ramsay Jones
2025-08-24 17:25 ` Patrick Steinhardt
2026-02-04 8:38 ` [PATCH v2] " Patrick Steinhardt
2026-02-04 10:00 ` Karthik Nayak
2026-02-04 11:56 ` Patrick Steinhardt
2026-02-04 17:53 ` Junio C Hamano
2026-02-05 6:58 ` Patrick Steinhardt
2026-02-05 9:37 ` Jeff King
2026-02-05 11:55 ` Patrick Steinhardt
2026-02-06 15:39 ` Patrick Steinhardt
2026-02-06 22:23 ` Junio C Hamano
2026-02-09 8:32 ` Patrick Steinhardt
2026-02-11 21:05 ` Junio C Hamano
2026-02-11 22:41 ` Johannes Sixt
2026-02-11 22:56 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqv7miatxa.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=ps@pks.im \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.