Mike Hommey <mh@xxxxxxxxxxxx> writes: > So, before I dive in, what would you think about such a feature? The daemon sitting on the other end to serve "git://" URL won't understand an attempt to push into. What goes over the wire in the fetch protocol does not give your updated "git push" enough information to guess what would happen if you pushed. Of course, it is open source and everything can be modified. You _could_ change the daemon whose primary purpose has been to serve fetch requests to also support dry-run only push to make what you outlined work. But isn't it adding unnecessary complexity for no real reason? It would be a tough sell, I would imagine. -- 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