From: david@lang.hm
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: unable to push
Date: Sun, 1 Jun 2008 11:34:19 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0806011133050.15294@asgard.lang.hm> (raw)
In-Reply-To: <20080601183134.GA2623@sigill.intra.peff.net>
On Sun, 1 Jun 2008, Jeff King wrote:
> On Sun, Jun 01, 2008 at 11:28:39AM -0700, david@lang.hm wrote:
>
>>> I'm not understanding that, either. You not only created localmaster,
>>> but you deleted master. Did you maybe do a "git branch -m"?
>>
>> in the public repo I had never created a 'master' branch. I had just done
>> a clone, setup git daemon, and pushed to it.
>
> Did you mean "init" here instead of clone? The clone should have created
> at least one branch (generally master, but depending on the current
> branch of the cloned repo).
no, it was definantly a clone, and it did not create a master branch (at
least not one that showed up with git branch -a)
David Lang
>> at some point several days later I found that my push didn't work and that
>> I wasn't on any branch in the public repo. in reading the man page for git
>> branch I saw the --track option, so I created the localmaster branch to
>> try and get things working.
>
> Ah, ok. That makes sense. The right fix was to just manually specify the
> refspec the first time ("git push public master") after which you could
> just do "git push public" if you wanted.
>
> -Peff
>
next prev parent reply other threads:[~2008-06-01 18:35 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 [this message]
2008-06-01 18:36 ` Jeff King
2008-05-31 16:52 ` Adam Piątyszek
2008-06-01 18:24 ` 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
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=alpine.DEB.1.10.0806011133050.15294@asgard.lang.hm \
--to=david@lang.hm \
--cc=git@vger.kernel.org \
--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.
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).