Re: git push [rejected] question

From: Jay Soffian <jaysoffian@gmail.com>
Date: Feb 19, 2008, 13:09 UTC
Message-ID: <76718490802190509k20225092o66853916f48e08b1@mail.gmail.com>
In-Reply-To: <20080219043353.GA23239@sigill.intra.peff.net>

On Feb 18, 2008 11:33 PM, Jeff King <peff@peff.net> wrote:

Show 9 quoted lines

> 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.