The most spectacular example of this is the command “git am”, which as far as I can tell, is something Linus hacked up and forced into the main codebase to solve a problem he was having one night. The various options of “git reset” do completely different things. Specifying filenames completely changes the semantics of some commands (“git commit” ignores local, unstaged changes in foo.txt “git commit foo.txt” doesn’t). But the shortcut for “git branch” combined with “git checkout”? “git checkout -b”.
Some “shortcuts” are graced with top level commands: “git pull” is exactly equivalent to “git fetch” followed by “git merge”. The command line syntax is completely arbitrary and inconsistent.
Now Git: you have files, a working tree, an index, a local repository, a remote repository, remotes (pointers to remote repositories), commits, treeishes (pointers to commits), branches, a stash… and you need to know all of it. In fact, branches are tags, and files you already know about, so you really need to learn three new things. That’s pretty much everything you need to know. As a point of reference, consider Subversion: you have files, a working directory, a repository, versions, branches, and tags. The information model is complicated – and you need to know all of it.
What a pity that it’s so hard to learn, has such an unpleasant command line interface, and treats its users with such utter contempt. It has a powerful distributed model which allows advanced users to do tricky things with branches, and rewriting history.
#Gitkraken file change code
Git is the source code version control system that is rapidly becoming the standard for open source projects.
0 kommentar(er)
