All:
Good morning! Yesterday was certainly a fun-filled knowledge intensive evening, all with a packed house! Many thanks to EdgeCase and Quick Solutions for making this happen, and to all the speakers (Greg, Kevin and Gayle), and most importantly the community.
Having said that, I will be posting the slides to my talk "Gittin' Git" somewhere soon, so you can get to them if you need to, but I wanted to post a few of the comments that I remember during and post talk -
[Ryan] - Do not use git commit -am unless you really really know what you are doing. This is a very good suggestion, and I am deliberating tweaking the slides to make a note of that.
[Ryan] - When working with remote repositories (like GitHub) make sure you have a clean repo before pulling in code. Avoids a lot of head-aches
[Joe] - With regards to feature set, learn one or two features, and learn to use them well. People will tell you all sorts of new things, but just pace along as you are comfortable. [My thought here - Kinda like emacs :D]
[Me] - Never never work in the master branch. Always create a new branch, and then merge back into the master. Creating, switching and deleting branches in Git is super easy and super fast. Use it.
[Mike] - (This was an offline comment) - Mike introduced me to GitX (
http://gitx.frim.nl/). This is a really nice UI tool for Mac OSX that helps you manage your repo.
(Please note that I am paraphrasing here :D). There were lots of other great questions and comments. Feel free to chime in with yours.
One final note - It seems that Code Jam, scheduled to happen next Wednesday, the 26th of August may not happen this month. I will be out of town this month, and with Joseph now in Arizona, its a little hard to organize. My apologies to all those who had planned on coming in. But there is always next month, or we can try and do something on the fly. As long as I am in town and available, I will make Integrallis' offices available for Code Jam.
Again, thank you all for being patient during my talk. Know that I am always available via email, and the Ruby community in Columbus has a number of experts in Git who might be willing to answer your questions. Now, git her done!
--
Raju