From: Takashi Iwai <tiwai@suse.de>
To: git@vger.kernel.org
Cc: Denton Liu <liu.denton@gmail.com>, Johannes Sixt <j6t@kdbg.org>,
Eric Huber <echuber2@illinois.edu>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Avi Halachmi <avihpit@yahoo.com>,
Christoph Sommer <sommer@cms-labs.org>,
Paul Mackerras <paulus@ozlabs.org>
Subject: [PATCH 0/2] gitk: Support of SHA256 repos
Date: Thu, 20 Mar 2025 16:41:32 +0100 [thread overview]
Message-ID: <20250320154136.23262-1-tiwai@suse.de> (raw)
Hi,
I recently stumbled on the problem of gitk with sha256 repo (while
testing the new openSUSE package git workflow that enforces SHA256);
gitk aborts immediately with a message "Can't parse git log output:
{commit xxx..}".
After skimming over the net, I found the patch [*] posted in 4 years
ago to add the support for sha256, but nothing happened since then,
unfortunately.
So here is the revived patch for gitk to add sha256 support, with
cleanups and corrections, in addition to the enhancement patch for the
missing auto-select length config for sha256.
Only lightly tested on a few sha256 repos.
Takashi
[*] https://patchwork.kernel.org/project/git/patch/pull.979.git.1623687519832.gitgitgadget@gmail.com
===
Rostislav Krasny (1):
gitk: Add a basic support of SHA256 repositories into Gitk
Takashi Iwai (1):
gitk: Add auto-select length preference for SHA256
gitk-git/gitk | 96 +++++++++++++++++++++++++++++++++++++--------------
1 file changed, 71 insertions(+), 25 deletions(-)
--
2.49.0
next reply other threads:[~2025-03-20 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 15:41 Takashi Iwai [this message]
2025-03-20 15:41 ` [PATCH 1/2] gitk: Add a basic support of SHA256 repositories into Gitk Takashi Iwai
2025-05-08 6:20 ` Johannes Sixt
2025-05-12 14:29 ` Takashi Iwai
2025-03-20 15:41 ` [PATCH 2/2] gitk: Add auto-select length preference for SHA256 Takashi Iwai
2025-05-08 6:20 ` Johannes Sixt
2025-05-12 14:36 ` Takashi Iwai
2025-05-08 6:21 ` [PATCH 0/2] gitk: Support of SHA256 repos Johannes Sixt
2025-05-12 14:45 ` Takashi Iwai
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=20250320154136.23262-1-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=avihpit@yahoo.com \
--cc=echuber2@illinois.edu \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=liu.denton@gmail.com \
--cc=paulus@ozlabs.org \
--cc=sommer@cms-labs.org \
/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 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 NNTP newsgroup(s).