Well the GUI's offer the same commands, they just have check boxes n such to select the different options of the command. I don't think it should matters if people learn the command line or GUI versions. Understanding what the commands do will happen more with practice. Reading the GIT online resources for the diagrams (example of one command [1]) helps to small degree.
Should we setup a junk repo for people to play with the commands? (a shared one like on a GITHub repo). I know people could go out and setup their own. But I mean a structured one with populated content that gets reset to a known state weekly or after its been used. It could allow for practiced scenarios. [1] http://git-scm.com/book/en/Git-Branching-Rebasing -Mark -----Original Message----- From: Nicholas Kwiatkowski [mailto:nicho...@spoon.as] Sent: Friday, April 05, 2013 8:11 AM To: dev@flex.apache.org Subject: Re: Still confused by git +1 on this. I've been sitting on the sidelines the last few weeks for that reason. I know there are a lot of standards that still need to be figured out, and since I'm very green with GIT, I don't really have the time at the moment to learn all the command line (i've been really busy with personal and professional stuff the last few weeks as well). My goal is not to use the command line, but use my IDE like I did before. Dropping to the command line and typing 10 commands every time I want to do something is a pain in the rear for those things that my IDE should be doing for me (I usually have a dozen command prompt windows open at any given time, but those are for truly interactive things). -Nick
