From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Nicolas Ratier <nicolas.ratier@femto-st.fr>, git@vger.kernel.org
Subject: Re: Problem with gitk
Date: Thu, 10 Jul 2025 08:59:29 -0700 [thread overview]
Message-ID: <xmqq1pqo82am.fsf@gitster.g> (raw)
In-Reply-To: <a6c5d181-5cdb-4070-96a6-cf88c3a5c838@kdbg.org> (Johannes Sixt's message of "Wed, 9 Jul 2025 17:08:20 +0200")
Johannes Sixt <j6t@kdbg.org> writes:
> Am 09.07.25 um 12:23 schrieb Nicolas Ratier:
>> I have this error with gitk :
>>
>> $ gitk
>>
>> and inside the window of gitk :
>>
>> Erreur à l'exécution de git log :
>>
>> wrong # args: should be
>>
>> "safe_open_command_redirect cmd redir"
>
> You are suffering from an incorrect backport of the recent security
> fixes to a Git version before 2.43.7. Tell your maintainer to look into
> this. I can help if necessary.
>
> For example, see here:
> https://bugs.launchpad.net/ubuntu/+source/git/+bug/2116253
>
> -- Hannes
Whew.
I first misread the above report and response and was afraid that we
started from an in-between version and botched our backport down to
older maintenance tracks, but after double checking that what we
shipped (Git 2.43.7 and upwards) recently does not have this issue,
I realized that there are distro packagers that backport even further
into the past, where some mistakes happened.
Thanks for a quick response.
next prev parent reply other threads:[~2025-07-10 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 10:23 Problem with gitk Nicolas Ratier
2025-07-09 15:08 ` Johannes Sixt
2025-07-10 15:59 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-28 20:40 Problem with GITK Paolo Ciarrocchi
2006-06-29 7:06 ` Uwe Zeisberger
2006-07-01 10:49 ` Paul Mackerras
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=xmqq1pqo82am.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=nicolas.ratier@femto-st.fr \
/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.