From: Junio C Hamano <gitster@pobox.com>
To: John Williams <john.williams@petalogix.com>
Cc: git@vger.kernel.org
Subject: Re: Wierd git over http behaviour
Date: Thu, 19 Feb 2009 22:23:23 -0800 [thread overview]
Message-ID: <7vab8hiq3o.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1d3f23370902192213g560020b3h7a2459c1439e5e5c@mail.gmail.com> (John Williams's message of "Fri, 20 Feb 2009 16:13:20 +1000")
John Williams <john.williams@petalogix.com> 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.
next prev parent reply other threads:[~2009-02-20 6:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 6:13 Wierd git over http behaviour John Williams
2009-02-20 6:23 ` Junio C Hamano [this message]
2009-02-24 5:45 ` John Williams
[not found] ` <bd6139dc0902192219m21c6b4e6ne9bcd2ca4ef6a9b5@mail.gmail.com>
[not found] ` <1d3f23370902192224g71270880p84e150af9640dec6@mail.gmail.com>
2009-02-20 6:39 ` Sverre Rabbelier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vab8hiq3o.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=john.williams@petalogix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).