From: Jeff King <peff@peff.net>
To: "Adam Piątyszek" <ediap@users.sourceforge.net>
Cc: david@lang.hm, git@vger.kernel.org
Subject: Re: unable to push
Date: Sun, 1 Jun 2008 14:24:17 -0400 [thread overview]
Message-ID: <20080601182417.GB742@sigill.intra.peff.net> (raw)
In-Reply-To: <48418242.1050606@users.sourceforge.net>
On Sat, May 31, 2008 at 06:52:18PM +0200, Adam Piątyszek wrote:
>>> root@asgard:/var/www/adastra/xml2pdf/current# git ls-remote public
>>> d3f3d8474db1c006a53be8b5f5c1a0d866d7e357 HEAD
>>> d3f3d8474db1c006a53be8b5f5c1a0d866d7e357 refs/heads/localmaster
>>
>> So you have only one branch, "localmaster".
>>
>>> root@asgard:/var/www/adastra/xml2pdf/current# git ls-remote .
>>> 71ab4eea48eb3407a2ff4eef2befe9251897d676 HEAD
>>> 71ab4eea48eb3407a2ff4eef2befe9251897d676 refs/heads/master
>>
>> But the remote has only one branch, "master".
>>
>> If you want to push your localmaster to his master, you can do:
>>
>> git push origin localmaster:master
> [...]
>
> I guess Peef described it the opposite way. In my opinion "localmaster"
> is the only branch on the remote "public" repository and the local
> repository has only one "master" branch.
Oh, sorry, I did totally read that backwards. So yes, there is a local
"master" branch but not a remote master branch (instead it has
"localmaster"). So the problem is the same (push without a refspec
pushes matching refs, and you don't have any matches) but the fix is, as
Adam pointed out:
> So to push local "master" to the remote "localmaster" branch you should use:
>
> git push public master:localmaster
Sorry for the confusion.
-Peff
prev parent reply other threads:[~2008-06-01 18:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 15:03 unable to push david
2008-05-31 15:50 ` Jeff King
2008-05-31 16:10 ` david
2008-06-01 18:22 ` Jeff King
2008-06-01 18:25 ` Jeff King
2008-06-01 18:28 ` david
2008-06-01 18:31 ` Jeff King
2008-06-01 18:34 ` david
2008-06-01 18:36 ` Jeff King
2008-05-31 16:52 ` Adam Piątyszek
2008-06-01 18:24 ` Jeff King [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080601182417.GB742@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=david@lang.hm \
--cc=ediap@users.sourceforge.net \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).