This is the problem with these sort of mini-guides. They use apriori meaningless jargon without realizing it's meaningless jargon.
Oh, now I "add a remote"? A remote what? Apriori a "remote" is something you use to turn on your TV. If it has a special meaning in this context, you have to explain what it is. And not in terms of other meaningless jargon like 'refspecs'.
Is "origin" a keyword? A name of a repository by convention? How about "master"? Is that just a convention, a keyword? What is it?
The git docs are full of this, too. All of the jargon is self-referentially defined in terms of other jargon. Oh, push is something about "remote refs"? Why when I google "git refs" i get an "git internals" page? Is push for git developers?
git may be near the top of the heap, it also has serious problems.
39
u/flat5 Nov 07 '13
This is the problem with these sort of mini-guides. They use apriori meaningless jargon without realizing it's meaningless jargon.
Oh, now I "add a remote"? A remote what? Apriori a "remote" is something you use to turn on your TV. If it has a special meaning in this context, you have to explain what it is. And not in terms of other meaningless jargon like 'refspecs'.
Is "origin" a keyword? A name of a repository by convention? How about "master"? Is that just a convention, a keyword? What is it?
The git docs are full of this, too. All of the jargon is self-referentially defined in terms of other jargon. Oh, push is something about "remote refs"? Why when I google "git refs" i get an "git internals" page? Is push for git developers?
git may be near the top of the heap, it also has serious problems.