Klemens Böswirth

> Something similar to doc/usecases/record_elektra but for applications and plugins using Elektra's API. I think you yourself would be much better suited for this. You definitely know of more actual...

I originally thought OpenSUSE Leap doesn't ship a package for `pkgconf`. But that seems to be incorrect, there is a package, but I missed it. However, we couldn't get Debian...

> It doesn't make sense to make them COW COW is still useful for saving memory when a copy is needed and change tracking definitely needs a copy. > The...

> I think for https://github.com/ElektraInitiative/libelektra/pull/4678, we first need to decide about read-only keys. One addition: @markus2330 Please stop suggestion more and more new decisions. At some point there has to...

Brilliant, I ask you to suggest fewer decisions so we can make some progress, and your response is suggesting another decision. I'm not even going to really respond to the...

> It is my responsibility that students I supervise do something useful in the context of scientific work, which requires as precondition: [...] What you did not mention here is...

@mpranj I took the `store_name.md` decision from you, because I'm working on a slightly broader decision for key names. It is also heavily related to the public API and the...

Couldn't @hannes99 swap the merge implementation in `kdb` while moving to C?

I think a big issue here is also that we often use e.g. `#include ` with ``. AFAIK the C standard doesn't have an opinion on this, but most compilers...

This issue is a bit outdated. We now have a few decisions that describe what the everything should look like: - [doc/decisions/3_decided/header_file_structure.md](https://github.com/ElektraInitiative/libelektra/blob/master/doc/decisions/3_decided/header_file_structure.md): Describes where the various header files should be...