Mike Hommey <mh@xxxxxxxxxxxx> writes: > Usually, when I run git push --dry-run, it's to check that what follows > (usually the refspec part) does what I want it to do, such as not pushing > tags I didn't intend to push(*), and stuff like that. Ahh, that one. That reminds me of a topic that we discussed but went away without reaching the conclusion on adding a "confirmation: are you sure this pushes what you want?" to the command. I had a doubt about the patch back then which was that it hardcoded a tty interaction and it would be hard to retrofit it to help GUI frontends (so my suggestion was to use something like hooks mechanism, perhaps --confirm=this-script and allow it to do its GUI thing), but thinking about it again, they can always use "expect" to drive the interaction with the confirmation prompt, so it may not a big deal after all---we might want to resurrect the topic. That was an unrelated, independent thought on your comment, but if we did so, you might not even have to try to use --dry-run on git:// transport. -- 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