Samuel Tardieu <sam@xxxxxxxxxxx> writes: > It looks like remote repositories are ordered alphabetically by their > local names when doing a "git remote update". Yeah, it is an unfortunate consequence of the Perl implementation that uses a hash to record remote and then try to give a stable ordering by sorting keys. The command originally was never intended for working on more than one remote, but addition of "remote update" could have been done to follow the order in the configuration. I think the reimplementaiton in 'next' that will hopefully be in 1.5.5 will keep the list of remotes in the order read from the config. -- 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
