12 ms·

Git Immersion

247 points by tortilla 16y ago

weixiyen 16y ago
All it has is a link to the download for git. Is this a placeholder for something?
- nonrecursive 16y ago
  Try the "start" arrow at the top
  - weixiyen 16y ago
    thanks
- johncoltrane 16y ago
  It's a Git tutorial. Click on the "START" black arrow to start the ride.
alanh 16y ago
Hmm, the chapter index uses the information (i) icon. Bizarre choice, but useful menu.
roel_v 16y ago
I've tried several times over the past couple of months to read articles or introductions to git. The one thing they seem to have in common is that it looks like they're having a contest on who can come up with the most outrageous ways of saying how bad other version control systems are. Anyway so I read through this whole website, but again this one fails to say: what does git do that others can't? Specifically, what is better about git than Subversion? There's the 'distributed' aspect which in some specific scenarios is nice. There seem to be some niceties like adding files to a commit one by one and doing a 'final' commit only at the end; that's a pain to do with the commandline subversion client (but it's really easy with Tortoisesvn). So, is there a concise explanation somewhere of what makes git better than subversion?
- mrchess 16y ago
  The only explanation needed is a fact. Linus Torvalds made git. Sold? :)
  - bradendouglass 16y ago
    Sold me
  - roel_v 16y ago
    Seriously? Are the upvotes because your comment was funny or is this actually a factor people make their tool choices on?
    - pyre 16y ago
      It could be due to Linus creating git for use on the Linux kernel. It's a huge project, and if the source control system can work for him it can work for others?
- kgrin 16y ago
  Branching works. I know it works in theory in SVN, but in practice one often runs into problems with any non-trivial branch. With git (or really DVCS), branching typically Just Works.
  - balac 16y ago
    The killer combination for me is branching + distributed. Your branches don't have to be mirrored on a remote server for all to see. Branching & merging are also insanely easy to do, so I find that I develop almost all new features in their own branch, and I can easily just throw them away if I want, I never did this with subversion.
  - roel_v 16y ago
    What are those problems? Why are they less with git? I often make branches with subversion; what goes wrong is keeping track of what features/changesets need to be merged across which branches, plus 'dependencies' of those changesets (changes in previous commits to the branch that add e.g. a class definition that the changesets depends on). Does git improve on that? How?
deleted 16y ago
[deleted]
bradendouglass 16y ago
A a well designed and simple GIT Tut this seems to be easy to run through. In addition, the steps are broken down into micro chunks which are always easier to people who have no clue. Wonderful and thank you.
ylem 16y ago
I found this to be a rather good tutorial!
cpeterso 16y ago
My favorite git introduction/reference is "Pro Git" by Scott Chacon. The book is available in print and online: http://progit.org/book/ http://progit.org/book/
lzell 16y ago
The ultimate log format (lab 10, item 4) is superb!
- brunoqc 16y ago
  I agree but I wonder if it would be prettier with colors. When I added this alias to my gitconfig I found an old alias I had for a pretty log, you may like it. http://www.jukie.net/bart/blog/pimping-out-git-log http://www.jukie.net/bart/blog/pimping-out-git-log
Lennie 16y ago
What are the downsides of git ? So far I only heared that git does not handle large binary files well and supposedly it is good to keep your large source tree (larger than the Linux-kernel !?) into many smaller git-repositories. And you have to learn something new and unlearn bad habbits. The no-easy-GUI-problem has been solved, right ?
- silentbicycle 16y ago
  It doesn't handle large binary files well, but would you track patches on them anyway? It doesn't fit git's model. Git deals with the current working state of the whole repository, not individual files. A major problem with git is that if you try to use it without realizing its fundamental model is different, it will seem awkward and complicated. Don't think about it as "like svn, but distributed"; start from zero.
  - Lennie 16y ago
    For some projects you also want to track versions of binary files because they go together with the code. And I read it was a bad idea to use git for those binary files, exactly because git was not designed for that.

Git Immersion

247 points by tortilla 16y ago

weixiyen 16y ago

All it has is a link to the download for git. Is this a placeholder for something?

nonrecursive 16y ago
Try the "start" arrow at the top
- weixiyen 16y ago
  thanks
johncoltrane 16y ago
It's a Git tutorial. Click on the "START" black arrow to start the ride.

alanh 16y ago

Hmm, the chapter index uses the information (i) icon. Bizarre choice, but useful menu.

roel_v 16y ago

I've tried several times over the past couple of months to read articles or introductions to git. The one thing they seem to have in common is that it looks like they're having a contest on who can come up with the most outrageous ways of saying how bad other version control systems are. Anyway so I read through this whole website, but again this one fails to say: what does git do that others can't? Specifically, what is better about git than Subversion? There's the 'distributed' aspect which in some specific scenarios is nice. There seem to be some niceties like adding files to a commit one by one and doing a 'final' commit only at the end; that's a pain to do with the commandline subversion client (but it's really easy with Tortoisesvn). So, is there a concise explanation somewhere of what makes git better than subversion?

mrchess 16y ago
The only explanation needed is a fact. Linus Torvalds made git. Sold? :)
- bradendouglass 16y ago
  Sold me
- roel_v 16y ago
  Seriously? Are the upvotes because your comment was funny or is this actually a factor people make their tool choices on?
  - pyre 16y ago
    It could be due to Linus creating git for use on the Linux kernel. It's a huge project, and if the source control system can work for him it can work for others?
kgrin 16y ago
Branching works. I know it works in theory in SVN, but in practice one often runs into problems with any non-trivial branch. With git (or really DVCS), branching typically Just Works.
- balac 16y ago
  The killer combination for me is branching + distributed. Your branches don't have to be mirrored on a remote server for all to see. Branching & merging are also insanely easy to do, so I find that I develop almost all new features in their own branch, and I can easily just throw them away if I want, I never did this with subversion.
- roel_v 16y ago
  What are those problems? Why are they less with git? I often make branches with subversion; what goes wrong is keeping track of what features/changesets need to be merged across which branches, plus 'dependencies' of those changesets (changes in previous commits to the branch that add e.g. a class definition that the changesets depends on). Does git improve on that? How?

deleted 16y ago

[deleted]

bradendouglass 16y ago

A a well designed and simple GIT Tut this seems to be easy to run through. In addition, the steps are broken down into micro chunks which are always easier to people who have no clue. Wonderful and thank you.

ylem 16y ago

I found this to be a rather good tutorial!

cpeterso 16y ago

My favorite git introduction/reference is "Pro Git" by Scott Chacon. The book is available in print and online: http://progit.org/book/ http://progit.org/book/

lzell 16y ago

The ultimate log format (lab 10, item 4) is superb!

brunoqc 16y ago
I agree but I wonder if it would be prettier with colors. When I added this alias to my gitconfig I found an old alias I had for a pretty log, you may like it. http://www.jukie.net/bart/blog/pimping-out-git-log http://www.jukie.net/bart/blog/pimping-out-git-log

Lennie 16y ago

What are the downsides of git ? So far I only heared that git does not handle large binary files well and supposedly it is good to keep your large source tree (larger than the Linux-kernel !?) into many smaller git-repositories. And you have to learn something new and unlearn bad habbits. The no-easy-GUI-problem has been solved, right ?

silentbicycle 16y ago
It doesn't handle large binary files well, but would you track patches on them anyway? It doesn't fit git's model. Git deals with the current working state of the whole repository, not individual files. A major problem with git is that if you try to use it without realizing its fundamental model is different, it will seem awkward and complicated. Don't think about it as "like svn, but distributed"; start from zero.
- Lennie 16y ago
  For some projects you also want to track versions of binary files because they go together with the code. And I read it was a bad idea to use git for those binary files, exactly because git was not designed for that.