It works if you do latex/makepdf from the parent directory. I've fixed this problem in my fork.

cool. im gonna try that later.
thanks duairc

it works.
on ubuntu 9.10, i had to install additional thing to run correctly: sudo apt-get install texlive-latex-recommended
otherwise i got an error below:

! LaTeX Error: File `kvoptions.sty` not found.

anyway now i can create a PDF with: ./latex/makepdf en

thanks duairc. closed.

No, adding a file will leave it unstaged. After 'git add file' it is staged. So we have to differentiate what we mean by add (file add or git add). In the diagram the 'file add' is meant.

No matter that it meant, git add both for modified files, and for untracked files, move the file to staged state. There is no apperation to make untracked file unmodifed without staging and commiting, so the image is deceptive.

In the chapter text we have: "If you run your status command again, you can see that your README file is now tracked and staged.". So the image not conflicts with the text too.

I also agree that the array should be connected to Staged.

this is what I said. but just adding the file (as mentioned in the diagram) will leave it unstaged. you have to make a git add to move to staged.
Ok, might be we have to differentiate again: adding a file (without modification) as a placeholder with a touch will leave it unstaged; adding a file by vi newfilename and put your code in there will be two steps in one. but its still unstaged. you have to make a git add to stage it. your referred sentence comes after the git add.

Adding the file do nothing. It just create the file. You can do anything with the file, but while it is not in the source control Git do nothing with it. It's untracked.
Unmodified files in the picture, are commited ones. You cannot commit the file without staging (ok, you can run git commit -a but it just make automaticaly staging for you, before the commiting).

ok,ok. but then we should draw it totally different: the 'add file' arrow should start before 'untracked' and end at 'modified'. As you said You cannot commit the file without staging .... To connect the 'add' arrow with 'staged' would imply that the staging will be done automatically.

ok, possible the solution is draw the commands on or above arrows, to make clean that the user done to process the file from state to state.

@fritzek: You are confusing what "add the file" means. When you say it, you mean creating an untracked file. When we say it, we mean turning an untracked file into a tracked file.

Notice that the "add the file" arrow goes from 'untracked' to 'unmodified'. It started at 'untracked', not at 'nonexistant'. There is no 'nonexistant' state in the diagram, because the diagram is concerned with the state of existing files only.

We are saying that running the 'git add' command on an untracked file makes it a staged file. This should be represented in the diagram as an arrow from untracked straight through to staged.

Clear enough now?

What do you mean by "src"? This is just text from a book. You can use any text editor. If you mean how to get the files onto your computer and work on it, just read the book.
What else do you wanna do with it?

Just wanted to know this https://github.github.com/github-flavored-markdown/

Thanks...