On Sun, Jul 22, 2012 at 2:18 AM, Thomas Ferris Nicolaisen
<tfn...@gmail.com>wrote:

> Well I can kinda see the parallel to vim when it comes to learning curve.
> Git certainly has some areas where the ui can be improved, and the good
> thing is that they are continuously making small steps to improve it (while
> vim is pretty frozen by now).
>

Thanks for your kind words Thomas!


>
> There are a few "modes" I often use. Git doesn't really call them modes,
> but I think of them like that as they are displayed in my console prompt
> (I've got some git-bash thing that shows off stuff like this in my ps1).
>
>
Could you point me to that 'git-bash thing'? -- Looks very useful


> # Detached head: not on a branch. Typically checked out an old commit.
> # am mode: in the middle of applying patches using git am
> # rebase: as discussed. Can also occur during git pull --rebase
> # conflict: when conflicts were found during merge
>

Yes this is the kind of thing I was asking about -- Say I do a pull and get
stuck on a conflict. Is there some easy way to find out what state (or as
you called it 'mode') git is in? Note that I may want to know this at a
different point of time from when the pull message is still in front of me
in the terminal.

Konstantin sorry to have caused offense. No intention of being sarcastic.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Reply via email to