Art, When git tells you it "failed to push some refs" that generally means that the remote repository has some changes that are not in your local repository. Do a "git pull" to get these changes brought in, have a look at the files it changed to make sure the changes didn't hurt anything (and if they did, fix it) then do your "git push".
There is a chapter on using Git in my "Making Sugar Activities" book. It may be helpful to you, and if it isn't your comments on what was missing would be helpful to me: http://objavi.flossmanuals.net/books/ActivitiesGuideSugar-en-2010.02.15-18.18.25.pdf It covers a lot of what you've just been through. James Simmons > Date: Thu, 18 Feb 2010 18:59:31 -0500 > From: "Art Hunkins" <abhun...@uncg.edu> > Subject: Re: [Sugar-devel] Setting public key - gitorious > To: "Aleksey Lim" <alsr...@member.fsf.org> > Cc: Sugar-devel@lists.sugarlabs.org > Message-ID: <8e06d06946ee4ecab2a72fb0c37c0...@art> > Content-Type: text/plain; format=flowed; charset="iso-8859-1"; > reply-type=original > > I did the "initial commit" with these results (similar to what I got > before): > > [o...@xo-05-25-69 ~]$ cd Activities/OurMusic.activity > [o...@xo-05-25-69 OurMusic.activity]$ git remote add origin > gitori...@git.sugarlabs.org:our-music/mainline.git > [o...@xo-05-25-69 OurMusic.activity]$ git push origin master > error: src refspec master does not match any. > fatal: The remote end hung up unexpectedly > error: failed to push some refs to > 'gitori...@git.sugarlabs.org:our-music/mainline.git' > > Is the problem perhaps that this is not an "initial commit"? I think I've > studied all available sugarlabs materials about git; unfortunately, Linux > terminology is still largely a foreign language to me, and I often don't > understand what's being said. (Sorry to be so unenlightened.) > > Art Hunkins _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
