lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <xmqqzfi89vsd.fsf@gitster.g>
Date: Wed, 26 Feb 2025 14:38:10 -0800
From: Junio C Hamano <gitster@...ox.com>
To: "D. Ben Knoble" <ben.knoble@...il.com>
Cc: git@...r.kernel.org,  Linux Kernel <linux-kernel@...r.kernel.org>,
  git-packagers@...glegroups.com
Subject: Re: [ANNOUNCE] Git v2.49.0-rc0

"D. Ben Knoble" <ben.knoble@...il.com> writes:
> [snip]
>>
>>  * "[help] autocorrect = 1" used to be a way to say "please wait for
> ...
> It seems "help.autocorrect" style is _usually_ preferred, but there
> are a handful of "[section] key" style. (I don't have a preference,
> just something I noticed.)

But you cannot write "help.autocorrect=1" and claim that it is
correct.  Your configuration file does not spell it that way, your
command line to "git config" command would not take it.

The more awkward "in the conifguration file it looks that way" needs
to be used when I need to write the variable with values.

Alternatively, I could say "setting help.autocorrect to 1 used to
be....".

Thanks.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ