From: Andreas Schwab <schwab@linux-m68k.org>
To: Alexey Kuznetsov <kuznetsov.alexey@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: clone bug
Date: Thu, 12 Jan 2012 15:36:46 +0100 [thread overview]
Message-ID: <m28vldj8ch.fsf@igel.home> (raw)
In-Reply-To: <CAO1Zr+pSLwRbsEZ_0LCeE2qLn+S=iMKVcMjqtYrmiBoQmjac_A@mail.gmail.com> (Alexey Kuznetsov's message of "Thu, 12 Jan 2012 16:43:50 +0300")
Alexey Kuznetsov <kuznetsov.alexey@gmail.com> writes:
> axet-laptop:123 axet$ git branch
> * master
> # git remote add common https://github.com/axet/common-bin.git
> # git fetch common
> From https://github.com/axet/common-bin
> * [new branch] master -> common/master
>
> ?? already strange master (local) to the remote common/master
The message means: the remote ref 'refs/heads/master' is stored locally
in 'refs/remotes/common/master'.
> axet-laptop:123 axet$ git push
> To https://github.com/axet/common-bin.git
> ! [rejected] master -> master (non-fast-forward)
"git push" is the same as "git push common" ('common' is the current
branch's remote). Since branch.master.push is not defined this then
uses the push.default config option to determine the action. The
default is 'matching', which means that local branch names are matched
against remote branch names. Local branch master matches remote branch
master. Note that this disregards the setting for
branch.master.upstream. If you do not want that you should set
push.default to 'upstream'.
See the examples in git-push(1) for more details.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2012-01-12 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 13:43 clone bug Alexey Kuznetsov
2012-01-12 14:32 ` Thomas Rast
2012-01-12 14:36 ` Andreas Schwab [this message]
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=m28vldj8ch.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=kuznetsov.alexey@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.