Hi,
there was discussion recently about the default behaviour of git-push
having the potential to confuse, making it easy to push commits that
are still cooking in other branches.

Its also possible for newbies to make mistakes with refspecs, but
there's no way to know if you've got the syntax right without actually
pushing. Steffan suggested a dry-run flag, which I've always wanted
too, so here's an attempt. Patches git-send-pack, git-push, their
docs, and adds a test for git-push.

Treat me gentle... first patch to the list and the mailer will
probably mangle it (sigh)

Cheers,
Baz

Diffstat:

 Documentation/git-push.txt      |    6 +++++-
 Documentation/git-send-pack.txt |    5 ++++-
 builtin-push.c                  |   10 ++++++++--
 send-pack.c                     |   31 +++++++++++++++++++------------
 t/t5516-fetch-push.sh           |   10 ++++++++++
 5 files changed, 46 insertions(+), 16 deletions(-)
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html