Have you read the pro git book? It's a really good and high quality book, it sure will be better than a tutorial. It goes from the basics to really deep subjects.
El mar., 25 de oct. de 2016 a la(s) 04:32, Gergely Polonkai < gerg...@polonkai.eu> escribió: > > > On Tue, Oct 25, 2016, 07:53 AD S <a...@radianweb.com.au> wrote: > > Honestly I must have watched hours of videos and completed 4 or 5 online > tutorials and it's still not clicking. > > > Could you show us which ones? The errors > > > I understand the concept: that git is a sub-versioning tool. It makes > sense. I know why one would use it. > > > Let's just call it Version Control System. subversion is another tool with > the same purpose. > > > But every time I try to use it something just breaks or goes wrong or > blows up. > > This has happened just this week, for example: > > > - Got error saying I was on the wrong branch, when I wasn't (this just > after a `git commit` command on a new branch). > > git never says you are on a wrong branch. Could you show us the exact > error message ? > > > - After a being able to commit and push to github all last week, I > randomly got a 'Connection refused' message (github.com was still up). > > There are tons of reasons that can lead to such an error message, most of > them being related to network issues, not Git. > > > - Went to pull 7 files from a branch but for some reason, this time, > it pulled hundreds of files from the whole, broader project. > > As commits are snapshots of the whole “project”, you can not pull changes > to only a set of files; you will get everything. > > > - A few times I got kicked out of the branch after a failed commit and > wouldn't let me return to branch because I had files waiting to be > committed. Only way was to hard reset. > > What do you mean “kicked out”? As Git does not have access control built > in, it cannot deny you from accessing a branch. Again, it would be helpful > to see an error message . > > > - Saying there are merge conflict issues, but not showing what files > there are on. > > git-merge output will not necessarily show you which files have conflicts > (although it is possible to parse it by eye). If you need such information, > use git status. > > > - Files that were tracked randomly become un-tracked. > > That means they were removed from tracking either by you or by someone > else, e.g. with git-rm > > These are a few, but in reality many similar problems happen throughout > the day which really impacts my productivity. When I started, and studied, > git I thought it would be pretty straight forward: pull the files you want > to work on, make changes, push them and if there is a conflict error fix > it. But it's complexity is beyond me. > > So, am I just cursed? What am I missing here? > > -- > 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 git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > -- > 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 git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
