Git has a somewhat steep learning curve, so I have seen teams having these problems (3+ hours a day), when no-one on the team was a "Git champion", and they were not willing to actually learn...
What kind of "strange issues" do you have to sort out? Do you have a common process for branching and merging? And do you have any education for "how to use Git" in your organisation? How many repos do you have? Do you use submodules or subtrees or neither or both? BR /Mattias Den torsdag 12 januari 2017 kl. 01:35:33 UTC+1 skrev AD S: > Hi all, > > Sorry I really don't mean for this to sound pessimistic or whiny - it > really is a genuine question. > > I come from a background of solo work where I didn't really use git all > that much. Now I work with a very large company and git is a huge part of > the workflow. > > However, I spend usually around 3hrs a day just trying to sort out strange > issues I come up against with git. Everyone else here just seems to think > this is par for the course, but it frustrates me a lot. > > Is this normal when working with large 100+ organisations? > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
