[FFmpeg-devel] ffmpegs future version control system

[Panagiotis Issaris]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi M?ns,

M?ns Rullg?rd wrote:
> Andy Parkins <andyparkins at gmail.com> writes:
> 
>> On Tuesday 2007, May 22, M?ns Rullg?rd wrote:
>>
>>>> Is that intentional, or could it be a git-http bug?
>>> That's odd, as they are the same repo.  What version of git are you
>>> running?
>> Could it be that the post-update hook isn't enabled in the repository?  
>> For dumb protocols (i.e. not git://) that have no way of negotiating 
>> missing revisions, the git-update-server-info script needs running to 
>> update the hints in .git/info/.
>>
>>  chmod a+x hooks/post-update
>>
>> Should be enough.
> 
> Thanks, hook enabled.  Let's see if it helps.

I just got a reply [1] from Johannes Schindelin:

"So, info/refs is still old. This file should have been updated by
git-update-server-info. I am not sure how this repo is updated, but I
suspect that the wrong hook contains the call to update-server-info, or
that the correct hook is not activated, or it does not have write
permission."


With friendly regards,
Takis

[1] http://article.gmane.org/gmane.comp.version-control.git/48266
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGVZxU9kOxLuzz4CkRAi5BAJ9TjEXM+GBVs4xeXyE/vGUycgQWQgCeIUs/
eJLv9SgIfK2NJUvMSnKctR8=
=Itm1
-----END PGP SIGNATURE-----