git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: david@lang.hm
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: unable to push
Date: Sat, 31 May 2008 09:10:26 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.1.10.0805310855000.15294@asgard.lang.hm> (raw)
In-Reply-To: <20080531155036.GA27397@sigill.intra.peff.net>

On Sat, 31 May 2008, Jeff King wrote:

> On Sat, May 31, 2008 at 08:03:47AM -0700, david@lang.hm wrote:
>
>> for some reason when I try to push to my public repo I get a message that
>> everything is up to date, but if I switch to that repo and do a pull it
>> updates properly
>
> If you "git push" without a refspec, it pushes "matching branches". See
> git-push(1) for more details.
>
>> 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
>
> You can also set it up permanently by adding a "remote.origin.push" line
> to your config file.
>
> But I do wonder why you don't just name your local branch "master" in
> the first place (it won't conflict in your local repo with the remote's
> master, which can be named as "origin/master").

I created localmaster in an attempt to get things working again. I'll try 
creating a new master branch... that does make it work again, thanks.

what I'm not understanding completely is how I broke things in the first 
place.

going back through .git/logs/HEAD it looks like I did a checkout HEAD^^^ 
and never properly recovered. should I have done a checkout master to get 
things back on track? I had thought that I could do a checkout of an old 
version, modify it, do a commit, and the commit would go on top of the old 
HEAD and I could just keep going (the reason for doing this instead of a 
reset is that I had already published the intermediate commits to the 
public repo, so I didn't want to roll back the history, just get the old 
version of one of the files)

>> root@asgard:/var/www/git/xml2pdf.git# git pull
>> remote: Counting objects: 8, done.
>> remote: Compressing objects: 100% (6/6), done.
>> remote: Total 6 (delta 4), reused 0 (delta 0)
>> Unpacking objects: 100% (6/6), done.
>> From /movies/www/adastra/xml2pdf/current/
>>    d3f3d84..71ab4ee  master     -> origin/master
>>  * [new tag]         1.8.5      -> 1.8.5
>> Updating d3f3d84..71ab4ee
>> Fast forward
>>  xml2pdf.pl |   22 +++++++++++-----------
>>  1 files changed, 11 insertions(+), 11 deletions(-)
>
> And this pulls from master -> localmaster, presumably because you have a
> branch.localmaster.merge config option (which is generally set up by
> default these days).

I manually setup the localmaster when I was having trouble getting things 
to work in either direction.

David Lang

  reply	other threads:[~2008-05-31 16:11 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 [this message]
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

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