On Thu, 9 Aug 2007, Evan Carroll wrote:
A disclaimer:: I could have mucked with anything, I will not place the blame on git as if I had strictly adhered to the tutorial instructions. Anything I did was through the UI, there was no mucking with files. Thanks in advance and good luck: I have one repos located on /var/git/scraper.git, it houses a small-inhouse project which I'm trying to use to sell git with. Unfortunately, I've had a very difficult time doing everything with git. Namely, pulling and pushing. It appears as if I git-clone this using the file-system (fs) addressing I get a repos which `git log` shows was last modified on Aug 9th. However, if I check this out with a git-clone using apache, which is simply hosting /var/git/scraper.git, I get a repos which was last updated on aug 7th - thus it is missing *a lot* of devel time. Now the 7th was when I created the --bare repos from my working directory git. All of the gits involved are using the latest stable version 1.5.2.4, they all built cleanly. The log is as follows:
Have you enabled the post-update hook on your server (chmod +X /var/git/scraper.git/hooks/post-update)? You need to run "git update-server-info" after updating a repo to allow clones via http to work properly. The default post-update hook does this for you.
-- Julian --- No, I do not know what the Schadenfreude is. Please tell me, because I'm dying to know. -- Homer Simpson When Flanders Failed - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
