From: Brandon C. <ca...@nr...> - 2008-03-17 17:28:11
|
Glenn Randers-Pehrson wrote: > There is a move afoot to put everything in a "git" repository but I don't > think that is going to help much (but it might). I have the "git" > repository ready to go, once someone sets up a "git" daemon It's possible to serve the repository using simple http. So if you want to put it out there as a work-in-progress repo that is possible. The repo _is_ the .git directory. So you just copy the .git directory in your repo to libpng.git somewhere on the web site. If you haven't already done so, you probably want to run 'git gc' to pack all loose objects first. There are a few things that should be done to minimize the download size for http clients, but as a work-in-progress repo, I wouldn't worry about them now. (what I'm talking about here is related to packs, and avoiding the situation where git clients using dumb http have to download the entire repo every time they update because the whole repo is in a single pack file). Then a client can do for example: git clone http://www.libpng.org/libpng.git my_libpng_repo Also, I agree with Bob, that regardless of public access, "version control" is surely a good thing. I'm hoping it will make things easier for Glenn including the 1.4.x re-sync. Admittedly, I haven't looked at the 1.4 branch, but ideally, you want to get to the point where you can pull updates and bug fixes from the 1.2 branch into the 1.4 branch. i.e. 'git pull . v1.2' from the v1.4 branch -brandon |