Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A simple guide for getting started with git

rogerdudler.github.com

Post reply on HN
Print view View original

71–80 of 132 posts

Re: A simple guide for getting started with git

#71

Post by aiscott »

brador wrote: post #66
aiscott wrote: post #58

Earlier quoted context omitted.

Really? You don't know what a repository is? Or are you just being hypothetically ignorant? I believe that somebody googling git usage is going to be a little bit conversant in the topic of version control.

Really. For me a repository is somewhere I might leave something...storage...like dropbox maybe? I don't know what it means in the github jargon sense. I have no idea what version control is specifically, but again, I guess it is v1.0 v2.0 etc.

I'm sorry for my attitude. There were some other posts that were doing the hypothetical thing and I guess I was having an allergic reaction.

I forget that this site is about startups and not specifically programmers or people with a heavy IT background.

It's my fault and I apologize.

Re: A simple guide for getting started with git

#72

Post by ereckers »

It looks like a lot of people have a case of the Mondays today. Seriously, these are about the number of commands I had sketched out when first starting on GIT, which I assume is your audience. I do have to say that I get a little tripped up between trying to use page-down and having to position the page. A full page side-swipe presentation format would work well here.

Re: A simple guide for getting started with git

#73

Post by dave1010uk »

zrail wrote: post #8
kruhft wrote: post #6

One thing that is missing is how to revert your working directory back to a tagged revision. Is that done with checkout?

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

Re: A simple guide for getting started with git

#74

Post by alexholehouse »

xradionut wrote: post #70

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.

It was available in paperback for free a few months ago too (may still be, not sure). I got it, for free, in Europe. From the states. I have no idea how that works financially, but it's a great book on a number of levels and Eric has my utmost respect because of it.

Re: A simple guide for getting started with git

#75

Post by g3orge »

skrebbel wrote: post #12

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…

Yes. But I think it mainly is a guide for starters with git. It is not supposed to be a full-on guide for source code management.

Re: A simple guide for getting started with git

#76

Post by VMG »

jasonkester wrote: post #68
tanoku wrote: 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…

Well, as a bearded guy from the 2010's, I prefer the command line to visual interfaces for the same reason I prefer C to LabVIEW.

Re: A simple guide for getting started with git

#77

Post by thomaslangston »

brador wrote: post #66
aiscott wrote: post #58

Earlier quoted context omitted.

Really? You don't know what a repository is? Or are you just being hypothetically ignorant? I believe that somebody googling git usage is going to be a little bit conversant in the topic of version control.

Really. For me a repository is somewhere I might leave something...storage...like dropbox maybe? I don't know what it means in the github jargon sense. I have no idea what version control is specifically, but again, I guess it is v1.0 v2.0 etc.

It is very much like dropbox, in that a repository is a special purpose folder that the git application can run against.

One difference is that you can have multiple of these folders, not only on your local machine but also on remote servers.

Re: A simple guide for getting started with git

#78

Post by necolas »

skrebbel wrote: post #12

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…

Your feedback is probably exactly what the project needs in order to become a better introductory guide. As such, I'm surprised the site doesn't include an obvious link to the GitHub repo/issues [1] so that people who have not been enlightened, or want to contribute better explanations, can share what needs to be clarified.

[1] https://github.com/rogerdudler/git-guide

Re: A simple guide for getting started with git

#79

Post by jff »

chadmaughan wrote: post #67

"There's just one thing, Dude. Do you have to use so many cuss words?" -- Big Lebowski Joking aside, there is really no need to ruin a great guide by swearing in the subtitle. I'm not sure I'll ever understand why developers think they need to swear in articles. In this instance, is it because the author is writing in nerd (addressing a seemingly technical concept) and needs to show his article has some universal acc…

Holy stuff, Batman, you're the guy using the word "doo-doo" unironically while asking adults to "show some maturity".
Post reply on HN