summaryrefslogtreecommitdiff
path: root/Documentation/glossary.txt
diff options
context:
space:
mode:
authorBrian Ewins <brian.ewins@gmail.com>2007-10-11 19:32:27 (GMT)
committerShawn O. Pearce <spearce@spearce.org>2007-10-16 02:02:52 (GMT)
commit11f2441f05ace25f1dae833a804761f1ca7d5cbb (patch)
tree043837d89e777bda9414b469c5be5cf812dc38f7 /Documentation/glossary.txt
parenta63103ae4f02f8890d381de352dbfc6cba0b646f (diff)
downloadgit-11f2441f05ace25f1dae833a804761f1ca7d5cbb.zip
git-11f2441f05ace25f1dae833a804761f1ca7d5cbb.tar.gz
git-11f2441f05ace25f1dae833a804761f1ca7d5cbb.tar.bz2
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>
Diffstat (limited to 'Documentation/glossary.txt')
0 files changed, 0 insertions, 0 deletions