I'll be interested to see what answers you get to this one. One of the projects I work on did the double whammy of moving to git and turning what had been a number of different version controlled projects into a single repository.
For an organisation split into geographicly distinct teams each working in a different part of a large codebase it hasn't felt like a natural fit.
Even using sparse checkouts we keep working round long checkout times, merge conflicts between teems seemingly unrelated to the changes made, timeouts fetching or checking out code and a lot of branches and check-in in the logs that makes it tricky to pick out the thread.
None of these are fatal, all are workable round but I guess it is just a nagging feeling that things are tougher than they need to be.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'll be interested to see what answers you get to this one. One of the projects I work on did the double whammy of moving to git and turning what had been a number of different version controlled projects into a single repository.
For an organisation split into geographicly distinct teams each working in a different part of a large codebase it hasn't felt like a natural fit.
Even using sparse checkouts we keep working round long checkout times, merge conflicts between teems seemingly unrelated to the changes made, timeouts fetching or checking out code and a lot of branches and check-in in the logs that makes it tricky to pick out the thread.
None of these are fatal, all are workable round but I guess it is just a nagging feeling that things are tougher than they need to be.