|eGit push going to refs/for/master instead of refs/head/master? [message #676373]
||Sat, 04 June 2011 01:05
| sneakyimp Mising name
Registered: December 2009
I installed eGit and then used File->import to import code from my core repository via ssh (it is hosted remotely). I chose to create a new eclipse project for the code ("new PHP project") and this seems to work fine.|
I then opened a file (which was fetched from the repos) in my new PHP project, made a change, and performed a commit. I added a comment and then right-clicked the root folder of my new PHP project and selected TEAM -> PUSH TO UPSTREAM.
The first time I tried this, the push operation timed out (and it was not possible to cancel it either) because the push uri assumed port 29418 even though I had specified port 22 when importing the code in the first place. That's problem #1.
The other problem is that the default refSpec appears to be HEAD:refs/for/master. what is the "for" path for? Forgive me, but I'm not even sure what the refSpec is for.
the bottom line is that my commit/push does effect my repository in that directories like these are created:
however, when i type "git log" these new commits just don't show up anywhere. I can see the "for" reference with this command:
prompt:/home/dev-core$ git show-ref
Just wondering why the default behavior of eGit is not to write to the head repository in my core?
Powered by FUDForum
. Page generated in 0.02586 seconds