| Name | 
 Last commit 
 | 
Last update | 
|---|---|---|
| .. | ||
| add.c | ||
| backend.c | ||
| conditionals.c | ||
| config_helpers.c | ||
| config_helpers.h | ||
| configlevel.c | ||
| global.c | ||
| include.c | ||
| memory.c | ||
| multivar.c | ||
| new.c | ||
| read.c | ||
| readonly.c | ||
| rename.c | ||
| snapshot.c | ||
| stress.c | ||
| validkeyname.c | ||
| write.c | 
When creating a new iterator for a config file backend, then we should always make sure that we're up to date by calling `config_refresh`. Otherwise, we might not notice when another process has modified the configuration file and thus will represent outdated values. Add two tests to config::stress that verify that we get up-to-date values when reading configuration entries via `git_config_iterator`.
| Name | 
 Last commit 
 | 
Last update | 
|---|---|---|
| .. | ||
| add.c | Loading commit data... | |
| backend.c | Loading commit data... | |
| conditionals.c | Loading commit data... | |
| config_helpers.c | Loading commit data... | |
| config_helpers.h | Loading commit data... | |
| configlevel.c | Loading commit data... | |
| global.c | Loading commit data... | |
| include.c | Loading commit data... | |
| memory.c | Loading commit data... | |
| multivar.c | Loading commit data... | |
| new.c | Loading commit data... | |
| read.c | Loading commit data... | |
| readonly.c | Loading commit data... | |
| rename.c | Loading commit data... | |
| snapshot.c | Loading commit data... | |
| stress.c | Loading commit data... | |
| validkeyname.c | Loading commit data... | |
| write.c | Loading commit data... |