Jakub Narebski <jnareb@xxxxxxxxx> writes: > Junio C Hamano wrote: >> Jakub Narebski <jnareb@xxxxxxxxx> writes: >> >> > But, if we change git_get_refs_list to do also work of git_get_references, >> > we should also change git_get_references to not use info/refs file at all >> > (it can, and usually for unknown reasons is stale) but always use >> > git-peek-remote, for consistency. >> >> Yes that would make sense. A repository served by gitweb does >> not necessarily has to serve objects over http transport, so it >> is nicer not to require info/refs to even exist or up to date. > > We do not require info/refs, as currently git_get_references falls > back to git-ls-remotes (should be git-peek-remote as it is faster) > if info/refs does not exist. But info/refs is usually stale; I guess > it is updated on pull/fetch/push, but not on commit. Yes, we are in agreement and are saying the same thing. - To unsubscribe from this list: 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