Is it practical to host a read-mostly git repo on a WAN-based distributed file system? The idea is that most developers would use the DFS-based repo to track the tip of the development stream, but only the integrator would publish updates to the DFS-based repo. As such, the need to repack the DFS-based repo will be somewhat, but not completely, reduced. Is this going to be practical, or are whole of repo operations eventually going to kill me because of latency and bandwidth issues associated with use of the DFS? Are there things I can do with the git configuration (such as limiting repacking behaviour) that will help? jon. -- 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