Continued thanks for all the help. I'm sorry to be so slow at this...I've 
just done very little command line operation in the past and probably 
shouldn't even be allowed near computers at all. I have very little 
experience on Linux/Unix as well, so I'm really floundering around in the 
dark here. I learned "ls" yesterday though, so I'm getting there.

So when you say "cmd.exe" you're talking about just a normal windows 
command line prompt? Like you go to Start and type "cmd"? I tried that 
initially but only got errors (e.g. "$" not recognized). Wasn't until I 
stumbled on the Git Bash thing that I could make Git work at all. 

I know there are GUI's available, but I have a big desire to develop some 
command line skills and this seems like a reasonable place to start. I 
figured how to commit files yesterday! Woo hoo! All that seemed to go 
reasonably well until I did the diff command, which had me lost until I 
finally typed "h" and got the help screen. 

On Tuesday, July 24, 2012 12:46:44 AM UTC-7, Konstantin Khomoutov wrote:
> On Mon, Jul 23, 2012 at 04:13:50PM -0700, Jeffery Brewer wrote: 
> > Aha! Figured out that after installing on windows you don't go to a 
> command 
> > line directly, you have to go through "Start > All Programs > Git > Git 
> > Bash" which gives you a different kind of command line. 
> [...] 
> Note that you don't *have to* use Git bash: everything just works in the 
> regular cmd.exe.  Actually, the existence of Git bash is due to some 
> parts of Git are written as Unix shell scripts so Git for Windows has to 
> ship with a shell implementing POSIX semantics. 
> There's no consensus in the Git for Windows community on what shell to 
> use for interactive work with Git.  I, for one, prefer cmd.exe as I tend 
> to use the shell not only for Git. 

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To view this discussion on the web visit
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to