Junio C Hamano wrote: > Jakub Narebski <jnareb@xxxxxxxxx> writes: >> So the new guidelines would be: >> * git_get_ prefix for subroutines related to git repository >> and returning single scalar (single value). >> * git_read_ prefix for subroutines related to git repository, reading some >> files or multiline output, and returning hash reference, or list >> reference, or list. > > I would suggest to use git_get for both, unless there is a good > reason to differenciate them, since I do not understand why you > would want to differenciate one value vs multivalue. I'd rather have git_read_info_refs, because it _reads_ info/refs file, and git_read_refs as opposed to git_get_hash/git_get_ref/git_ref_to_hash (or hash_from_ref). I'm not sure about git_read_projects vs. perhaps git_get_project_list or git_list_projects. Neither about git_read_description vs. git_get_project_description -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html