[Sugar-devel] Setting public key - gitorious
abhunkin at uncg.edu
Fri Feb 19 14:32:41 EST 2010
The Git chapter in your manual is excellent, and I've learned a lot from it.
It presents a coherent, continuous view of the subject, and is very
readable. It should be grasped by anyone with a modest acquaintance of
things Linux. (Unfortunately, I'm not quite there yet. My problem is that
I'm still not conversant in the language.)
One of my challenges is that I've been using the Nano editor rather than one
more fully-featured. OTOH, I'm also doing most things on the XO-1 and wanted
(also perhaps wrongly) to keep things as simple and minimal as possible.
I think my basic push/pull problem was that I had confused my own activity
versions, and had tried to push a version that had *no changes* from the
current git posting. (I presume that would give the error message I got as
well.) Yes, on your suggestion and Aleksey's, I added the pull first. At any
rate, when I committed some actual *changes*, the error disappeared - only
to show the remaining ssh key issue.
Maybe *some* day -- (and thanks for your help and wonderful tutorial)
----- Original Message -----
From: "James Simmons" <nicestep at gmail.com>
To: <sugar-devel at lists.sugarlabs.org>
Sent: Friday, February 19, 2010 11:29 AM
Subject: Re: [Sugar-devel] Setting public key - gitorious
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:
It covers a lot of what you've just been through.
> Date: Thu, 18 Feb 2010 18:59:31 -0500
> From: "Art Hunkins" <abhunkin at uncg.edu>
> Subject: Re: [Sugar-devel] Setting public key - gitorious
> To: "Aleksey Lim" <alsroot at member.fsf.org>
> Cc: Sugar-devel at lists.sugarlabs.org
> Message-ID: <8E06D06946EE4ECAB2A72FB0C37C0590 at Art>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> I did the "initial commit" with these results (similar to what I got
> [olpc at xo-05-25-69 ~]$ cd Activities/OurMusic.activity
> [olpc at xo-05-25-69 OurMusic.activity]$ git remote add origin
> gitorious at git.sugarlabs.org:our-music/mainline.git
> [olpc at 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
> 'gitorious at 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 at lists.sugarlabs.org
More information about the Sugar-devel