Fernando Zamora

In my previous post I discussed the steps necessary to create a Git repository.   As it turns out, today I found the other piece of information that I was missing. That is, that when you create a central repository it must be bare. If you really want to share code (collaborate with others) in a repository, your "master" or central repository should be an empty one.  That means that the only thing that it should contain is the repository but no source files (or any other files under version control).  If you will recall, I ran into some hair-pulling problems because I couldn't push to the master repository. That was because the master branch had a working directory that had the master branch checked out.  As a result, Git refused to push changes made in the slave to the master.  By creating a bare repository you are insuring that this repository will not be worked on directly (i.e. it does not have a working directory).  Therefore by creating a bare repository you will

About three weeks ago or so I decided to get started with Git.  After all, it seems that everyone else is using it and I felt that at the very least I should investigate it and play around with it a little.  I didn't know what the best approach was to for my research.  Little did I know that it was going to be a difficult journey, especially since I am doing all of this research on my own time instead of during work hours.  Also because Git is so robust and has so many different ways of doing the most basic things. At first I took advantage of my Safari Books Online account to read Scott Chacon's Pro Git.  I found it to be a difficult read as a beginner.  It became easier to digest once I'd gone a couple of rounds with Git.  I also found out that the book is available for free online at the Pro Git Website .  Recently I also received some hints to other resources such as the CoDe Magazine article,  Git for SubVersion Users , by Derick Bailey  and also to the  Alamo Coders

I just recently learned about JSIL, after attending the August 2011  CTXNA users group.  I am really excited about JSIL because it will allow me to broaden my game audience.  I haven't yet converted any of my games, but I am in the process of setting up JSIL.  What I have learned so far just in getting it setup is that you must clone the JSIL repository and include the sub modules. At first I was only cloning the directory without the recursive attribute and as a result I was missing several projects in my solution. I used the following command to download it with the sub modules: c:\mydir\>git clone https://github.com/kevingadd/JSIL.git --recursive After downloading it, my build was still failing because it did not have reference to XNA 3.x framework (I only have the XNA 4.0 framework).  For some reason, JSIL references XNA 3.x framework in one of the projects (Proxies.XNA3).  Therefore I had to download and install the XNA 3.x Game Studio.  If someone else knows a be