Live data from Hacker News

A simple guide for getting started with git

rogerdudler.github.com

111–120 of 132 posts

Re: A simple guide for getting started with git

#111
post #8

Earlier quoted context omitted.

Moving between refs is almost always done with checkout git checkout tag-name Tags are just a fancy label pointing to a commit so you can use them anywhere you'd use a sha1 or branch name.

Or, if you don't want to keep untracked files: git reset --hard

Please note that this does more then what the parent suggests doing by "git checkout".

This destroys untracked changes and resets your current branch-pointer to , removing all the commit-history that comes after . (You can still recover them from the database, e.g. with "git reflog")

Re: A simple guide for getting started with git

#112

I think git is not easy to use, and the proof of that is that at least once a month there is a "how to use git" tutorial on the front-page of HN. I'm not saying git is a totally bad system, but I disagree with people who think git is easy to use. You don't see thousands of tutorials on the web, and tutorials hitting the HN frontpage on "How to use Subversion", "My personal Subversion workflow", "My .bashrc file conta…

> I think git is not easy to use, and the proof of that is that at least once a month there is a "how to use git" tutorial on the front-page of HN.

The command line is hard to learn, and there is no real way to learn it besides... well, learning it by heart, quirks and all. A bit like learning a foreign language. After a while, you don't notice it any more and you realize how powerful and pleasant git really is.

Here is an article that captures these thoughts fairly well:

http://beust.com/weblog/2010/04/06/git-for-the-nervous-devel...

Re: A simple guide for getting started with git

#113
I love this, and I've bookmarked it to email it around when I need to, but I'd love to read something that simplifies setting up git on the server side as a central location for repositories.

But that aside, coming from SVN it makes sense to me, and I've played around with git without really reading into it too much. It's of added interest because deployment and branching seems much less of a hassle with git than with svn.

Re: A simple guide for getting started with git

#114

I don't get this. Sure, the tutorial looks very pretty, but it does not explain any concepts. "Create a new repository." What is a repository? What do I do with it? The HEAD is a tree "which points to the last commit you've made". Huh? A tree can point? The one in my garden can't. Also, what's a commit? I thought "commit" was a verb, not a noun. And so on. It's nice that people want to make something as complex as gi…

looks like this is a list of "how to" instructions than why use git. take it for what it is.

I actually have used both tortoiseSVN and git, and I'm actually in love with git!

you should give it a try.

Re: A simple guide for getting started with git

#115

I wish git (and mercurial for that matter) could properly backup large files. I have some sql files > 100MB that I can't check into source control.

Why not?

edit: I use git for game development, and we check in some big asset files (uncompressed .wav music tracks etc.). As long as these don't change too often, the repo stays manageable. Up to 10gigs is still a reasonable repository size IMO.

Re: A simple guide for getting started with git

#116

Why not just download Eric Sink's "Version Control by Example" ? http://www.ericsink.com/vcbe/ The book is free or can be purchased and explains both git and Mercurial with similar examples. We use it at our office to get novices up to speed on source control.

This is such a great book. No fluff, just straightforward examples of how to do basic version control. Plus, Eric is a good writer. (Actually, anyone who can take a dull topic like version control and make it entertaining probably qualifies as a great writer.)

Re: A simple guide for getting started with git

#117

I love this, and I've bookmarked it to email it around when I need to, but I'd love to read something that simplifies setting up git on the server side as a central location for repositories. But that aside, coming from SVN it makes sense to me, and I've played around with git without really reading into it too much. It's of added interest because deployment and branching seems much less of a hassle with git than wit…

Git is a decentralized scm. It means there's no concept of a central repository. You can push and pull between any repositories.

A good reading is the online book Pro Git which has been mentioned in the comments.

Re: A simple guide for getting started with git

#119
post #60

Earlier quoted context omitted.

> I don't have to actually type commands into a command prompt like some bearded guy from the '70s Really? I mean, really?

Absolutely. I am aware that lots of developers seem to like the command line, but I can't for the life of me understand why. I think visually, so looking at a visual interface such as Windows Explorer is several orders of magnitude more productive than fiddling around with cd/ls to give me a picture of what's going on. Once I find what I'm looking for, I'd much prefer to right click on it and get on with my day than…

do you write your programs in sharepoint designer, too? ;)
Post reply on HN