News for hackers. Stuff that matters.
Re:Git koans by aidenn0 on Monday April 08, 2013 @12:16PM (#5512610)
What you described is how git thinks of branches.

Most developers think of branches as something they commit to. Therefore they are surprised when later they can't tell which branch they committed to.

This could trivially be fixed with porcelain that puts the name of the branch the commit was made to at the end of the commit message.

The issue of branches not really being branches is not unique to git; most VCs I've ever used have had significant differences between what you would think of as a branch and actual branches (SVN doesn't even have branches, except as a convention).

Re:Git koans by philwelch on Monday April 08, 2013 @02:57PM (#5513711)
Git is predicated on the notion that it's actually quite simple and elegant how Git works, and programmers are clever enough to understand how their software works, so not much porcelain is necessary. There's a refreshing honesty to that.
Re:Git koans by aidenn0 on Tuesday April 09, 2013 @01:30AM (#5516596)
That's not my understanding of it's history; it was originally planned to have, potentially, multiple porcelains, but that idea died of a couple years back.
Re:Git koans by philwelch on Tuesday April 09, 2013 @01:23PM (#5519582)
It was discovered more or less by accident, I think. Similar to the story of M-expressions in Lisp: http://en.wikipedia.org/wiki/M-expression
Re:Git koans by qznc on Wednesday April 10, 2013 @07:38AM (#5524473)
I believe that is the root problem of git. Originally, the assumption was: porcelains will provide a nice UI, so core git can leak implementation details. However, it turns out the implementation details are so simple and intuitive for many developers that core git is now the dominant UI.

For example, the multiple use cases of 'checkout' or 'reset' are quite intuitive, if you have the implementation in mind.

Re:Git koans by duaneb on Monday April 08, 2013 @05:23PM (#5514711)
I have no idea how git works. Where do they tell you? I'm curious to learn.
Re:Git koans by Aga on Monday April 08, 2013 @07:14PM (#5515370)
I have found the Pro Git book to be the best: http://git-scm.com/book

That, and constantly creating your own test repositories to test new commands/concepts. With a distributed VCS it's easy and fast. Just run "git init test" somewhere and start committing!

I also recommend you to use "gitk" when you're learning to constantly look at your history tree. That should clarify the concept "branches are pointers" after a few tests.

Re:Git koans by qznc on Wednesday April 10, 2013 @07:12AM (#5524382)
Git for computer scientists: http://eagain.net/articles/git-for-computer-scientists/

Quick introduction to git internals for people who are not scared by words like Directed Acyclic Graph.

Re:Git koans by duaneb on Wednesday April 10, 2013 @04:05PM (#5527759)
Thanks, that's perfect. I don't as much care about the nitty gritty at the moment as a conceptual overview of the architecture of git.