| commit | 11f2441f05ace25f1dae833a804761f1ca7d5cbb | |
| author | Brian Ewins <brian.ewins@gmail.com> | |
| Thu, 11 Oct 2007 19:32:27 +0000 (11 20:32 +0100) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Tue, 16 Oct 2007 02:02:52 +0000 (15 22:02 -0400) | ||
| tree | 043837d89e777bda9414b469c5be5cf812dc38f7 | treesnapshot (tar.gz zip) |
| parent | a63103ae4f02f8890d381de352dbfc6cba0b646f | commitdiff |
Add a --dry-run option to git-push.
The default behaviour of git-push is potentially confusing
for new users, since it will push changes that are not on
the current branch. Publishing patches that were still
cooking on a development branch is hard to undo.
It would also be nice to be able to verify the expansion
of refspecs if you've edited them, so that you know
what branches matched on the server.
Adding a --dry-run flag allows the user to experiment
safely and learn how to use git-push properly. Originally
suggested by Steffen Prohaska.
Signed-off-by: Brian Ewins <brian.ewins@gmail.com>
Signed-off-by: Lars Hjemli <hjemli@gmail.com>
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
The default behaviour of git-push is potentially confusing
for new users, since it will push changes that are not on
the current branch. Publishing patches that were still
cooking on a development branch is hard to undo.
It would also be nice to be able to verify the expansion
of refspecs if you've edited them, so that you know
what branches matched on the server.
Adding a --dry-run flag allows the user to experiment
safely and learn how to use git-push properly. Originally
suggested by Steffen Prohaska.
Signed-off-by: Brian Ewins <brian.ewins@gmail.com>
Signed-off-by: Lars Hjemli <hjemli@gmail.com>
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| Documentation/git-push.txt | diffblobblamehistory | |
| builtin-push.c | diffblobblamehistory | |
| t/t5516-fetch-push.sh | diffblobblamehistory |