On Monday, October 29, 2012 11:31:13 PM UTC+1, kramer.newsreader wrote:

> I am a fairly experienced developer and I have never had issues working 
> with source control tools before git.
> I take a new job.  I am working with git.  I am thinking about quitting 
> over having to use it.

I'm afraid your employer has done a poor job here. If they weren't 
interested in giving you the necessary training for the job, they could at 
least have configured and set things up for you, with a couple of git 
commands to get things done. This is fully possible, and you should give 
this feedback to them (and if they don't listen to feedback like that, you 
probably should quit anyway).

> Every source control tool I have used before has an easy command that 
> says: "Use these changes right here.  Yes there are conflicts, but these 
> are correct."

Yeah, SVN has about a handful of commands you need for day-to-day work. For 
Git you need 5 just to get started, then another 5 when it comes to 
collaborating with others, and then another 5 for good measure. 

The reason for this is Git's feature-richness. I like to say Git is not 
complex, it is simple multiplied by 20. At its core, it's just a graph with 
three kinds of objects, and all those commands operate on this elegant data 
structure. However, that's something you start to realize after using Git 
for several months. 

> How can I get to "Not currently on any branch" when I was on a branch and 
> didn't ask to switch branches?

There are several modes in Git that can detach you from a branch to go 
travelling down history, for good reasons:

* git checkout <commit, or tag>, will check out code as it was at some 
point (not necessarily a branch)
* git bisect, will go through history scanning for the introduction of a bug
* git rebase, will rewrite history, and can leave you in an in-between 
state where you have to resolve conflicts

Not sure which one it was, maybe it was a git pull --rebase? Please provide 
us with your history and we might be able to explain.

> Where is that with git?

It will all make sense at some point :)

> Why is the git information model SO COMPLICATED?

The model isn't so complicated. The problem is that there are so many 
features, and you haven't used these features before (even when you think 
they are the equivalent of something in SVN/CVS/whatever, they probably are 

> Why can't there be a way to 

Usually, there's a way to do everything in Git :)

> Why is the documentation so inadequate?

Now this one ain't right. There are loooads of documentation. I personally 
like the git-scm.com/pro-git book, a great 
introduction: http://git-scm.com/book

Here's another easy guide for just getting started in 
Git: http://rogerdudler.github.com/git-guide/ (more links at the bottom of 
the guide)

And here's another more extensive guide: http://think-like-a-git.net/
There are also a handful of books you can buy, and a gazillion more guides 
and articles on the internet. Plus an answer for every question you could 
ever think of on stackoverflow.com.

If you don't know where to start, a good place is here on this mailing list.

> Why do I have to be a source control engineer just to be a software 
> developer?
You don't have to. Either, your company's source control engineer (who 
should be a Git guru) should set you up so you don't have to think so much 
about these things. 

If you have to learn it by yourself anyhow, there might be some relief in 
knowing that there is no other source-control system people will fall so 
much in love with after learning it :)

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 git-users@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to