John Williams <john.williams@xxxxxxxxxxxxx> writes:
> Strange thing is, when doing an http fetch of said tree, it gets no updates
> to the tree later than about Jan 13 this year, even though the tree itself
> has many, many commits since then (its origin is Linus's tree and we pull
> regularly). Heads created later than that date are also not visible (doing
> git branch -a) in the clone pulled over http. Clones made using git: are
> fine.
Most likely you would want to run git-update-server-info from
project.git/hooks/post-update hook. A sample shipped with git looks like:
#!/bin/sh
#
# An example hook script to prepare a packed repository for use over
# dumb transports.
#
# To enable this hook, rename this file to "post-update".
exec git-update-server-info
make sure it is executable.
$ cd linux-2.6-microblaze.git/hooks
$ ls -l post-update
$ chmod +x post-update
And then run "git update-server-info" just once in the repository. I see
it was run on Jan 22nd and not since then, but the latest of your refs
have Feb 19th timestamp. Every time somebody pushes into this repository,
you would need to run the command, and post-update hook is a standard way
to do so easily.
--
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
