From: "Jay Soffian" <jaysoffian@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: "Jason Garber" <jgarber@ionzoft.com>, git@vger.kernel.org
Subject: Re: git push [rejected] question
Date: Tue, 19 Feb 2008 08:09:36 -0500 [thread overview]
Message-ID: <76718490802190509k20225092o66853916f48e08b1@mail.gmail.com> (raw)
In-Reply-To: <20080219043353.GA23239@sigill.intra.peff.net>
On Feb 18, 2008 11:33 PM, Jeff King <peff@peff.net> wrote:
> I think the user is missing one fundamental aspect of pushing: the
> behavior of "git push" without any refspecs specified is to push all
> matching refs (i.e., if you have branch refs/heads/Issue/Default and so
> does the remote, then it will attempt to push). So no matter what branch
> he is on when doing the push, it tries to push many such branches.
>
> If you want to push just the current branch, try:
>
> git push origin HEAD
git-push(1) is a bit confusing I think:
"Note: If no explicit refspec is found, (that is neither on the command line
nor in any Push line of the corresponding remotes file---see below), then all
the heads that exist both on the local side and on the remote side are
updated."
is clear enough, but then:
"--all Instead of naming each ref to push, specifies that all refs under
$GIT_DIR/refs/heads/ be pushed."
So what is '--all' needed for then?
It seems like the default should be to push just the current branch
... this would correspond to what a user of git pull expects (even
though the converse of git-push is really git-fetch, for a new user,
that might not be entirely clear).
j.
next prev parent reply other threads:[~2008-02-19 13:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 22:15 git push [rejected] question Jason Garber
2008-02-19 4:33 ` Jeff King
2008-02-19 13:09 ` Jay Soffian [this message]
2008-02-19 15:08 ` Jeff King
2008-02-19 15:18 ` Jay Soffian
2008-02-19 15:25 ` Jeff King
2008-02-19 15:59 ` Johannes Schindelin
2008-02-19 16:14 ` [PATCH(TIC)] push: annoy all users by deprecating the default semantics Johannes Schindelin
2008-02-19 16:21 ` Jason Garber
2008-02-19 16:41 ` Johannes Schindelin
2008-02-19 16:37 ` Jeff King
2008-02-19 16:54 ` Johannes Schindelin
2008-02-19 17:05 ` Jeff King
2008-02-20 1:03 ` Govind Salinas
2008-02-20 1:10 ` Junio C Hamano
2008-02-20 1:21 ` Govind Salinas
2008-02-20 3:15 ` Junio C Hamano
2008-02-19 18:40 ` Jay Soffian
[not found] ` <E7DE807861E8474E8AC3DC7AC2C75EE50542F62D@34093-EVS2C1.exchange.rackspace.com>
2008-02-19 15:21 ` git push [rejected] question Jeff King
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=76718490802190509k20225092o66853916f48e08b1@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.org \
--cc=jgarber@ionzoft.com \
--cc=peff@peff.net \
/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).