Re:Why SQLite Does Not Use Git
by friend-monoid on Wednesday April 11, 2018 @03:11AM
(#16808755)
But they are also called symbolic refs in git terminology...
[ Parent
| on HN ]
A symbolic ref is a ref that points to another ref instead of a ref that points to a commit. `HEAD` is a symbolic ref. (It should be your only symbolic ref.)
Re:Why SQLite Does Not Use Git
by friend-monoid on Wednesday April 11, 2018 @12:34PM
(#16812819)
Unless it is detached. :)
That term makes sense.
But just as you wouldn't call a symlink to a zip archive a zip file itself, you also shouldn't call a branch a ref.
Re:Why SQLite Does Not Use Git
by friend-monoid on Wednesday April 11, 2018 @11:56AM
(#16812394)
Hrm, but a ref is a file containing a hash, right? So if the hash is equivalent to the file, the surely a ref is equivalent to a symlink? A symbolic ref, in turn, should be a symlink to a symlink... Or something like that...
A ref points to an object.
That object doesn't change unless the hashing algo was tricked.
A branch points to anything you want it to point to. It can be any ref you want and can be changed at will.
Re:Why SQLite Does Not Use Git
by friend-monoid on Wednesday April 11, 2018 @05:42PM
(#16816017)
sha1 - object (e.g. 5a480efb...)
file with sha1 - ref (e.g. master)
file with ref - symbolic ref (e.g. HEAD)
right? Seeing as you can git update-ref branches, but you need to git symbolic-ref HEAD.
Re:Why SQLite Does Not Use Git
by rantanplan on Wednesday April 11, 2018 @07:42AM
(#16810122)
But it is a ref. It's an alias for the last commit of a particular timeline, as I said above.
Re:Why SQLite Does Not Use Git
by cup-of-tea on Wednesday April 11, 2018 @07:06AM
(#16809857)
So would you rather say a branch is a commit?