6 ms·
> (actually, I didn't completely give up, I just browsed the Github mirror, which was the only usable part of their version control). What makes our git own g
by anarazel 9y ago
> (actually, I didn't completely give up, I just browsed the Github mirror, which was the only usable part of their version control).
What makes our git own git repo unusable?
https://git.postgresql.org/gitweb/?p=postgresql.git; https://git.postgresql.org/gitweb/?p=postgresql.git;
I personally find that quicker to get around in than github.
- kazinator 9y agoMan, why doesn't gitweb serve up the clone links as links that you can right click and copy? You have to swipe the cursor over "https://git.postgresql.org/git/postgresql.git" https://git.postgresql.org/git/postgresql.git" and copy; how lame. CGIT is so much nicer. It also serves up tarballs out of tags. If you do a "git tag foo-123" and push it out, then on your CGIT interface, there will be a foo-123.tar.gz URL for download (as well as .bz2 and .zip), pulled right out of the repo. Still, either is light years ahead of github's presentation of repos. > What makes our git own git repo unusable? I know; WTF? From grandparent's comment I got the impression that Postgresql must be using CVS, or just tarballs in a FTP directory or something (and that someone kindly made a git repo and put it into GH).