Junio C Hamano <gitster@xxxxxxxxx> writes: > $ git push --dry-run sf.net > warning: You did not specify any refspecs to push, and the current remote > warning: has not configured any push refspecs. The default action in this > warning: case is to push all matching refspecs, that is, all branches > warning: that exist both locally and remotely will be updated. This may > warning: not necessarily be what you want to happen. > warning: > warning: You can specify what action you want to take in this case, and > warning: avoid seeing this message again, by configuring 'push.default' to: > warning: 'nothing' : Do not push anythig > warning: 'matching' : Push all matching branches (default) > warning: 'tracking' : Push the current branch to whatever it is tracking > warning: 'current' : Push the current branch > fatal: 'sf.net' does not appear to be a git repository > fatal: The remote end hung up unexpectedly > > The final, most important error messages are dwarfed out by the warning > that talks about setting configuration on the remote that does not even > exist. Actually, I take it back. It is still annoying, but the point of these warning lines is to warn even for a one-off push you make to a place without having any [remote "sf.net"] entry anywhere in the config. In the worst case, the above "sf.net" may even be just a full URL of the remote, and we do want to trigger the warning. So this is not even a usability bug. Sorry for a thinko. -- 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
