Tina Müller (tinita)

@parrenin > So I concatenate the general parameter file with each individual parameter file which thus overwrite the general parameter file when there is a duplicate entry I think this...

The YAML 1.1 spec also says that keys should be unique: https://yaml.org/spec/1.1/#id861060 > The content of a mapping node is an unordered set of key: value node pairs, with the...

@wimglenn the correct way to use multiple merge keys is actually: ``` - k: v extra: # merged vars from blob0 + blob1

@wimglenn Duplicates should only be considered in the actual mapping definition itself. Merge keys are explicitly there for merging, so they should *override* keys. By the way, the spec https://yaml.org/type/merge.html...

@alexchandel yes, but it's not that trivial to implement, if we want to keep merge key functionality as well. Like I said earlier https://github.com/yaml/pyyaml/issues/165#issuecomment-525047100

Good idea! I'm working on getting this into openSUSE too https://build.opensuse.org/package/show/home:tinita:branches:devel:tools:scm/git-subrepo

> 2.17 is the oldest version of git that is supported Did you mean 2.7?

@admorgan We are modifying the shebang of all scripts to use the actual program instead of env. It would of course work with `env`. But using `env` in distribution packages...

True, there are such use cases. But if you are using homebrew on a system to install a newer bash, you can also install the git-subrepo package with homebrew. Packages...

Hm, I'm having a problem with the zsh completion on openSUSE. ``` git subrepo GIT_SUBREPO_ROOT is null; has `/path/to/git-subrepo/.rc` been sourced? ``` I wonder if that is still necessary: https://github.com/ingydotnet/git-subrepo/blob/master/share/zsh-completion/_git-subrepo#L6-L9...