Comments on: GIT sucks

By: git smash | Scott James Remnant

git smash | Scott James Remnant — Mon, 06 Feb 2012 18:21:35 +0000

[...] still sucks though. This entry was posted in Technology by scott. Bookmark the [...]

By: Tom Troller

Tom Troller — Wed, 01 Feb 2012 04:16:00 +0000

No, you are retarded, git is fine.

By: Bob

Bob — Wed, 11 Jan 2012 03:50:08 +0000

A-fucking-men. Linux is full of whackos and really shitty software. I’d use SVN over GIT any day.

By: brianko

brianko — Sun, 25 Dec 2011 17:16:29 +0000

Haha…here I am, after several hours of trying to figure out how the hell to create a working copy from a repo I just made. git pull? git fetch? I dunno…many tutorials, and not a single one seems to address something as simple as “how the FUCK do I make a copy of my shiny new repo and get productive work done?” Sorry, world…git might be the shit, but I’ll stick with svn, thank you very much.

And my favorite Christmas present? Typing in “git sucks” and landing on this page. That certainly made my day.

By: Git Hater

Git Hater — Sat, 17 Dec 2011 05:28:01 +0000

I wholeheartedly agree. I’m a contractor, who wants to get paid for software development not waste hours on git.

By: Alex J

Alex J — Sat, 10 Dec 2011 02:24:46 +0000

Agree on every word. git wastes hours and hours of our development time. It was developed by Linus and Co for their specific needs – merging huge Linux branches and replace bitkeeper. Workflows are illogical and overcomplicated. Try to for instance check out a remote branch. Does anybody remember the right command line keys from memory? I doubt that. People who in love with git are either those who know all guts and bolts of it and sit on git mailing list watching for every single change or those who do merging of branches day and night.

By: Phillip Susi

Phillip Susi — Sun, 04 Dec 2011 16:31:40 +0000

Indeed, the more I use it, the more awesome it is, but yes, it can also be very frustrating trying to figure things out by reading the very legalese man pages.

By the way Scott, a simple git init foo.git ( no environment variables needed ) on the server, and a git push –mirror are all you needed. If you are wondering why the remote HEAD isn’t set without –mirror, it is because unlike BZR, a GIT repo isn’t limited to a single branch, so normally when you push, you just want to add or update a specific branch, not set the default branch on the remote repo. You also could have cloned from the HEADless repo by specifying the branch you wanted.

By: Yawar

Yawar — Mon, 14 Nov 2011 03:23:12 +0000

It's a little bit of a bummer to see people still having so much trouble with Git: once I learned to see the commits as nodes in a DAG and the branches as pointers to specific nodes, it just clicked for me, and my usual Git workflow is nice and smooth. I hope you come across some good tutorials. I like John Wiegley's Git from the bottom up because it really brings across the idea that you're really manipulating very simple structures in Git. And most of the time you can even just ignore blobs and trees and just focus on commits and how they're related.

By: rolfen

rolfen — Mon, 17 Oct 2011 21:27:47 +0000

Git is easy to set up and use locally, but a huge pain for pushing stuff. If it wasn’t easy to set up and use locally it would not stand a chance.

By: Git… enough! – The Scribbler of the Rueful Countenance

Git… enough! – The Scribbler of the Rueful Countenance — Wed, 28 Sep 2011 01:45:25 +0000

[...] which are completely orthogonal to actually getting work done. This is evidenced by all the blog posts written by people being frustrated with git. As the renowned 20th century mathematician G. H. Hardy [...]