I agree that renaming this to `git_config_get_multivar_foreach` seems like a reasonable blend of the git_config naming scheme and the rest of the libgit2 naming scheme. Keeping the old name, particularly when you're introducing this new iterator-based API, seems inconsistent with the rest of libgit2.

However, I'm not a huge fan of reusing the old API name for the new one that constructs the iterator. I know we're pre 1.0 and all that, but (a) it would be nicer to avoid reusing the name, and (b) the `git_config_get_multivar` name doesn't seem self-consistent with `git_config_iterator_new` that is added to get a general iterator. I'm somewhat at a loss to pick a better name for the multivar iterator constructor, though. Since it seems like it is just, in some sense, a subset of `git_config_iterator_glob_new`, maybe `git_config_iterator_multivar_new`? Actually, I see that's not the case, but let's talk about that elsewhere.

As a probably-too-radical alternative, we could remove the "get" part of API names and go with `git_config_string`, `git_config_int32`, `git_config_bool`, etc. as the getters. Then the names that @ben recommended would make sense - `git_config_multivar_foreach` and `git_config_multivar_iterator_new`. We'd end up with pairs like `git_config_string` / `git_config_set_string` which don't bother me.