From: Baz <brian.ewins@gmail.com>
To: "GIT list" <git@vger.kernel.org>
Cc: "Junio C Hamano" <gitster@pobox.com>
Subject: [PATCH 0/2] Add --dry-run option to git-push
Date: Thu, 11 Oct 2007 00:34:27 +0100 [thread overview]
Message-ID: <2faad3050710101634s5ed39bcbn723184810bc265d5@mail.gmail.com> (raw)
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(-)
next reply other threads:[~2007-10-10 23:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 23:34 Baz [this message]
2007-10-11 7:57 ` [PATCH 0/2] Add --dry-run option to git-push Lars Hjemli
[not found] ` <16913589bee1374245d8b8f7333ab3984b56ffcb.1192130892.git.Brian.Ewins@gmail.com>
2007-10-11 19:32 ` [PATCH v2 1/2] Add a --dry-run option to git-send-pack Brian Ewins
2007-10-11 20:18 ` Lars Hjemli
[not found] ` <fe9a919ada9f6b6a79d9810eda11c13fb1091103.1192130892.git.Brian.Ewins@gmail.com>
2007-10-11 19:32 ` [PATCH v2 2/2] Add a --dry-run option to git-push Brian Ewins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2faad3050710101634s5ed39bcbn723184810bc265d5@mail.gmail.com \
--to=brian.ewins@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).