From: Mike Hommey <mh@glandium.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Allowing push --dry-run through fetch url
Date: Fri, 6 Nov 2009 10:53:57 +0100 [thread overview]
Message-ID: <20091106095357.GA13389@glandium.org> (raw)
In-Reply-To: <7vfx8s0yy1.fsf@alter.siamese.dyndns.org>
On Fri, Nov 06, 2009 at 01:44:54AM -0800, Junio C Hamano wrote:
<snip>
> But doesn't "branch -v" give the necessary information for that purpose
> and even a bit more? Couldn't "git fetch && git branch -v" be a better
> solution for your real problem "X"?
Usually, when I run git push --dry-run, it's to check that what follows
(usually the refspec part) does what I want it to do, such as not pushing
tags I didn't intend to push(*), and stuff like that.
Mike
(*) the fact that all tags from all remotes are being mixed doesn't help,
here, and without dry-running, I end up pushing tags from one remote onto
another.
next prev parent reply other threads:[~2009-11-06 9:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 7:37 Allowing push --dry-run through fetch url Mike Hommey
2009-11-06 8:49 ` Junio C Hamano
2009-11-06 8:59 ` Mike Hommey
2009-11-06 9:02 ` Junio C Hamano
2009-11-06 9:21 ` Mike Hommey
2009-11-06 9:44 ` Junio C Hamano
2009-11-06 9:53 ` Mike Hommey [this message]
2009-11-08 19:23 ` Junio C Hamano
2009-11-09 7:56 ` Mike Hommey
2009-12-29 11:05 ` Nanako Shiraishi
2009-12-29 16:58 ` Junio C Hamano
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=20091106095357.GA13389@glandium.org \
--to=mh@glandium.org \
--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).