Doing the Git exercise in class was pretty cool. Luckily I have used git before, so I am pretty familiar with the syntax as well as how it works. Once my RSA key was registered, I had a fairly easy time of pulling down the repo and editing files to be pushed back out. My group members seemed to grasp the concepts very quickly as well, so it was not difficult for us all to work around each others changes. We had very few conflicts when making changes.
The one thing that seemed to get me, as well as another of my group members, was when we were setting the git config stuff, we both accidentally set out user.name variable to “color.ui” because we misread the instructions. So when we pushed committed changes to the repository, our names showed up as “color.ui” instead of our actual user names. Once we went into the config file and made the proper changes, all went smoothly. The actual git part of the assignment was not difficult. I think by the end of the class almost our entire group had added a separate file to the repo and also edited a common file so we could all see each others changes.
I’m looking forward to actually using git with this project because I have only used it on a very large scale at work. So I think using it in class on a smaller repository will be much more interesting because I will actually be able to tell exactly what was changed at a quick glance. Also, I am wondering if we are going to be committing patches or if we will simply do a git commit of our changes and then push them out to the repo. At work, I am used to doing a git format-patch HEAD^ and generating a patch for review before it is added to the repository, however it seems like the way we are doing it in class is a little more straightforward, even if it is more likely that someone will commit code that doesn’t work 100%. It would be nice if there was a designated person in the group to review the patches before committing them so that someone doesn’t push out something broken and overwrite good code. I guess that will have to be up to the group members to investigate how well the code works before pushing it out.
Looking forward to getting started!
From the blog trevorhodde by Trevor and used with permission of the author. All other rights reserved by the author.