From: Panagiotis Issaris <takis.issaris@uhasselt.be>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: HTTP trees trailing GIT trees
Date: Wed, 23 May 2007 16:11:12 +0200 [thread overview]
Message-ID: <46544B80.90907@uhasselt.be> (raw)
In-Reply-To: <20070523140552.GN4489@pasky.or.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Petr Baudis wrote:
> Hi,
>
> On Wed, May 23, 2007 at 04:01:33PM CEST, Panagiotis Issaris wrote:
>> I reported this to the person who had setup the repository:
>> http://article.gmane.org/gmane.comp.video.ffmpeg.devel/51151
>>
>> But unfortunately, the problem seems to remain.
>>
>> Is this a known problem, or might this be a bug or misconfiguration?
>
> did any push happenned since the post-update hook was enabled? It
> takes effect only after the next push. So far,
>
> http://git.mplayerhq.hu/ffmpeg/info/refs
>
> and
>
> http://git.mplayerhq.hu/ffmpeg/refs/heads/master
>
> is still out-of-sync (keeping this in sync is what is the job of the
> post-update hook, or git-update-server-info respectively).
Yes, I'd think so, as Måns stated that he had enabled the hook on
2007-05-22 20:43:27. The last commit shown on http://git.mplayerhq.hu/
through gitweb occurred 25 minutes ago ("Wed, 23 May 2007 13:46:11 +0000").
Thanks for your fast reply.
With friendly regards,
Takis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGVEuA9kOxLuzz4CkRAkXTAJ9xqbkUO6qF88HwV7GSYnVkV+VRNgCfSr/D
ZPPYBfeD9RpqbXNKwmukObc=
=wkyo
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-05-23 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 14:01 HTTP trees trailing GIT trees Panagiotis Issaris
2007-05-23 14:05 ` Petr Baudis
2007-05-23 14:11 ` Panagiotis Issaris [this message]
2007-05-23 14:15 ` Panagiotis Issaris
2007-05-24 12:44 ` Panagiotis Issaris
2007-05-24 13:57 ` Johannes Schindelin
2007-05-24 14:19 ` Panagiotis Issaris
2007-05-25 11:15 ` Jakub Narebski
2007-05-25 12:36 ` Johannes Schindelin
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=46544B80.90907@uhasselt.be \
--to=takis.issaris@uhasselt.be \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.