![]() submitting your dev branch's differences from the official repo) the github inteface works very well. When I read that part, I knew EXACTLY why Linus would say this. example follows.įrom the article: you should never ever use the github interfaces to merge anything (but that doesn't take the sting out of it the first time you sit down to use it.) However, the choice of nomenclature does begin to make more sense the more you become steeped in git. So there is learning involved (the choice of nomenclature just makes things that much more uncomfortable). (there are some of those floating around though) To the git project's credit there are very good tutorials to help you make friends with it, but the downside is they are some 30 page tutorials that are not geared to answer "the top 10 things you normally need to know to use git". The git command line is its own little language. The git nomenclature does suck! Not that it is bad, but that it is completely non-intuitive for someone who may otherwise be very skilled and fluent in a number of other projects that are now hosted on Github. You wouldn't sit down to write something in C having only a passing knowledge of the language, or you wouldn't write a Bind config or zone file without significant effort to learn the lingo of the Berkeley DNS named server. The CLI for git is a fantastic tool, but just like any advanced piece of software, you have to make friends with it first.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |