https://public-inbox.org/git/xmqqpodnvmmw.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx/ for context why we need a new data field. Implement that. Once upon a time we had a long discussion where to put documentation best. The answer was header files as there documentation has less chance to become stale and be out of date. Improve the docs by * migrating them to the header * clarifying how the compare function is to be used * how the arguments to hashmap_get/remove should be used. Thanks, Stefan Stefan Beller (2): hashmap.h: compare function has access to a data field hashmap: migrate documentation from Documentation/technical into header Documentation/technical/api-hashmap.txt | 309 -------------------------------- attr.c | 4 +- builtin/describe.c | 6 +- builtin/difftool.c | 20 ++- builtin/fast-export.c | 5 +- config.c | 7 +- convert.c | 3 +- diffcore-rename.c | 2 +- hashmap.c | 17 +- hashmap.h | 256 +++++++++++++++++++++++--- name-hash.c | 12 +- oidset.c | 5 +- patch-ids.c | 6 +- refs.c | 4 +- remote.c | 7 +- sha1_file.c | 5 +- sub-process.c | 5 +- sub-process.h | 6 +- submodule-config.c | 10 +- t/helper/test-hashmap.c | 15 +- 20 files changed, 325 insertions(+), 379 deletions(-) delete mode 100644 Documentation/technical/api-hashmap.txt -- 2.13.0.31.g9b732c453e
