The flow chart on Sharing a public Git repo over HTTP came about because a friend asked me how to do it and I hadn’t gotten to writing that part of the Git book yet. It ended up a flow chart because I happen to like making them. Anyway, I’ve reached the point that all authors reach (with probably every book) where finishing the thing has become “work”. But, I love helping out other geeks, and I need to get this finished. So, if you’ve got Git questions, that you can’t easily figure out from the docs, please send them my way. It’ll give me incentive to write the remaining stuff or improve the existing. I’ll try and get an answer to you within a day. All I ask is that you give me feedback on whatever I respond with because it’s probably going to end up in the book. ;)
Just drop me an e-mail to masukomi @ masukomi.org
OK, a bit lazy here.
I have been using CVS on and off for a long time; so using git is a bit confusing.
If all the repo clones are equivalent, how does one know one is the ‘clean’ repo? On CVS, there is a centralised repo lying somewhere.
I can’t seem to wrap my head around the decentralised model.
Sivaram
Another question.
Is it possible to clone only the HEAD or the latest version of code instead of the entire history?
Other than doing an export and then doing a git –init again?
Sivaram,
Regarding the second question on how to export the current tree without history. Use “git-archive”, this will export the tree as a .tar.gz.
Kapil. –
Name (required)
Mail (will not be published) (required)
Website
