That worked like a charm!  I'm brand new to Git, so some of the stuff
with remote repositories is still pretty new to me.  Let me explain
how I'm expecting to manage my CakePHP project's repository, and let
me know if I'm completely off the deep end!

First, I'll create my central repository for my project as a bare
clone from CakePHP:
  git clone --bare [email protected]:cakephp.git myproject

Then I'll create my own working copy by cloning that:
  git clone myu...@myserver:myproject.git

I do a bunch of work in my local copy, then commit and push back to my
own central repo:
  git commit -a
  git push

To get all the changes other devs have committed to my own central
repo, I pull:
  git pull
  (OR: git fetch; git merge origin/master)

To merge the latest changes from CakePHP's repo into my own central
repo, I fetch directly into my own central repo from Cake's:
  git fetch [email protected]:cakephp.git

Does all that look right?


Ben Dilts

On Aug 13, 3:23 am, majna <[email protected]> wrote:
> check out thishttp://thechaw.com/wiki/guides/setup
>
> On Aug 13, 1:21 am, BeanDog <[email protected]> wrote:
>
>
>
> > The new CakePHP code site,http://code.cakephp.org/source, says to use
> > "git clone [email protected]:cakephp.git" to get a copy of the code
> > (I assume that's the latest 1.2 stable code).  However, when I try to
> > do that, I get the following error:
>
> > Permission denied (publickey).
> > fatal: The remote end hung up unexpectedly
>
> > Am I doing something wrong?  Is this not the best public place to git
> > the source code for CakePHP?  I was hoping switching to git would make
> > keeping the CakePHP core in my project up to date much easier.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to