Re: What's cooking in git.git (Dec 2020, #04; Tue, 22)

[Patrick Steinhardt <ps@pks.im>]

[-- Attachment #1: Type: text/plain, Size: 1602 bytes --]

On Tue, Dec 22, 2020 at 12:07:21PM -0800, Junio C Hamano wrote:
> * jk/disambiguate-equal-in-config-param (2020-12-09) 3 commits
>  - config: store "git -c" variables using more robust format
>  - config: parse more robust format in GIT_CONFIG_PARAMETERS
>  - quote: make sq_dequote_step() a public function
>  (this branch uses ps/config-env-pairs.)
> 
>  The quoting rules used to pass "git -c var=val" configuration
>  across processes have been updated in a backward compatible way, so
>  that the value read from an environment variable can contain an
>  equal sign when using the "git --config-env var=env" feature.
> 
>  We may want to make this just a middle part of the
>  ps/config-env-pairs topic with a bit of patch shuffling.

Please note that this has already happened with v5 of my patch series
[1], which I've sent out last week. So you may want to swap out those
two series and use the combined v5 as it also improves documentation.

[1]: https://public-inbox.org/git/cover.1608104755.git.ps@pks.im/

Patrick

> * ps/config-env-pairs (2020-12-09) 6 commits
>  - config: allow specifying config entries via envvar pairs
>  - config: refactor parsing of GIT_CONFIG_PARAMETERS
>  - config: extract function to parse config pairs
>  - environment: make `getenv_safe()` non-static
>  - config: add new way to pass config via `--config-env`
>  - git: add `--super-prefix` to usage string
>  (this branch is used by jk/disambiguate-equal-in-config-param.)
> 
>  Introduce two new ways to feed configuration variable-value pairs
>  via environment variables.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]