git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Takashi Iwai <tiwai@suse.de>,
	git@vger.kernel.org, Denton Liu <liu.denton@gmail.com>,
	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: Re: [PATCH 2/2] gitk: Add auto-select length preference for SHA256
Date: Mon, 12 May 2025 16:36:44 +0200	[thread overview]
Message-ID: <87tt5puc8z.wl-tiwai@suse.de> (raw)
In-Reply-To: <d3922b07-d9eb-477c-aa91-35ea709ad626@kdbg.org>

On Thu, 08 May 2025 08:20:57 +0200,
Johannes Sixt wrote:
> 
> Am 20.03.25 um 16:41 schrieb Takashi Iwai:
> > This implements the missing preference setup of the auto select length
> > for SHA256. The variable set via the preference menu is switched
> > depending on the hash algorithm.
> > 
> > The default auto-select length is set to 64 for SHA256, and
> > saved/restored as "autosellensha256" in the config.
> 
> I think the purpose of this change is to offer different settings for
> the selected length depending on the hash algorithm. If that is the
> case, the commit message could do a better job describing that: it says
> only what happens implementationwise, but not what the user sees.

Sure, I can rephrase.  Could you suggest a better text example?

> I do not think this is necessary. If I had set the option to, say, 12, I
> would not want it to be set to something else when I go to a repository
> that has a different hash algorithm.

The problem is that a value 40 is used always as default even for
SHA256.  So, without this change, the selection looks always shorter
than the full ID unless you explicitly change this option in the
configuration menu.  That sucks.

> (But I do not know for certain,
> because I do not have any SHA256 repositories, yet.)

You can find SHA256 git repos in src.opensuse.org, where we started
hitting the problems with gitk :)
For example, one of my repos below is very small:
  https://src.opensuse.org/kernel-firmware/kernel-firmware-all


thanks,

Takashi

  reply	other threads:[~2025-05-12 14:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-20 15:41 [PATCH 0/2] gitk: Support of SHA256 repos Takashi Iwai
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 [this message]
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=87tt5puc8z.wl-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).