Name |
Last commit
|
Last update |
---|---|---|
include | ||
src | ||
tests | ||
.HEADER | ||
.gitignore | ||
CMakeLists.txt | ||
CONVENTIONS | ||
COPYING | ||
README.md | ||
api.doxygen | ||
git.git-authors | ||
libgit2.pc.in | ||
waf | ||
wscript |
Such a list preserves the order the variables were first read in which will be useful later for merging different data-sets. Furthermore, reading and writing out the same configuration should not reorganize the variables, which could happen when iterating through all the items in a hash table. A hash table is overkill for this small a data-set anyway. Signed-off-by: Carlos Martín Nieto <cmn@elego.de>
Name |
Last commit
|
Last update |
---|---|---|
include | Loading commit data... | |
src | Loading commit data... | |
tests | Loading commit data... | |
.HEADER | Loading commit data... | |
.gitignore | Loading commit data... | |
CMakeLists.txt | Loading commit data... | |
CONVENTIONS | Loading commit data... | |
COPYING | Loading commit data... | |
README.md | Loading commit data... | |
api.doxygen | Loading commit data... | |
git.git-authors | Loading commit data... | |
libgit2.pc.in | Loading commit data... | |
waf | Loading commit data... | |
wscript | Loading commit data... |