It looks like remote repositories are ordered alphabetically by their local names when doing a "git remote update". In a project I follow, it has an unfortunate consequence: a dumb remote repository using "http://"; is fetched first, while many commits are shared between all the upstreams I follow. If remotes were fetched using their order in .git/config, it would fetch from a "git://" remote repository first, limiting transfers from the dumb remote repository. Is there a way to force the update order short of changing the local names or issuing multiple fetch commands? Sam -- Samuel Tardieu -- sam@xxxxxxxxxxx -- http://www.rfc1149.net/ -- 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
