| commit | 72de5ce81b7bb1421a0d2b627af5e8b776f0ef55 | |
| author | Ivan Zakharyaschev <imz@altlinux.org> | |
| Thu, 20 May 2010 13:30:45 +0000 (20 13:30 +0000) | ||
| committer | Ivan Zakharyaschev <imz@altlinux.org> | |
| Thu, 20 May 2010 13:30:45 +0000 (20 13:30 +0000) | ||
| tree | 583ff0f99e4dc46e7f9053c5138c7281af5a0c4d | treesnapshot (tar.gz zip) |
| parent | 104375c036f8bcc6953720ff20ae8797d48329d6 | commitdiff |
Do its best to detect the default case and to push to 'origin'
then. Unclear error messages will appear less often as a consequence.
But it can't parse "git push"'s options (with parameters) perfectly
(without additional info), so you might need to specify a remote
explicitly.
(FR: git commands should print out the specification of options in the
format accepted by "git rev-parse --parseopt", then one could more
easily implement extensions to the git commands, like this one.)
then. Unclear error messages will appear less often as a consequence.
But it can't parse "git push"'s options (with parameters) perfectly
(without additional info), so you might need to specify a remote
explicitly.
(FR: git commands should print out the specification of options in the
format accepted by "git rev-parse --parseopt", then one could more
easily implement extensions to the git commands, like this one.)
| git-push-as-remote | diffblobblamehistory |