From: Konstantin Khomoutov <flatworm@users.sourceforge.net>
To: Ryan Jacobs <ryan.mjacobs@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git push --all --tags
Date: Sat, 15 Nov 2014 18:58:36 +0300 [thread overview]
Message-ID: <20141115185836.103fc4f493ad55725eab38f0@domain007.com> (raw)
In-Reply-To: <loom.20141115T054352-272@post.gmane.org>
On Sat, 15 Nov 2014 04:44:19 +0000 (UTC)
Ryan Jacobs <ryan.mjacobs@gmail.com> wrote:
> $ git push --all --tags
> error: --all and --tags are incompatible
>
> Why are these flags incompatible? Just wondering 'cause I think that
> it would be a good feature to be able to push all of your branches
> and all of your tags to the server in one quick and simple command.
git push --mirror
should do this.
next prev parent reply other threads:[~2014-11-15 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 4:44 git push --all --tags Ryan Jacobs
2014-11-15 15:58 ` Konstantin Khomoutov [this message]
2014-11-15 17:56 ` Scott Schmit
2014-11-15 18:33 ` Andreas Schwab
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=20141115185836.103fc4f493ad55725eab38f0@domain007.com \
--to=flatworm@users.sourceforge.net \
--cc=git@vger.kernel.org \
--cc=ryan.mjacobs@gmail.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).