From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: HTTP trees trailing GIT trees
Date: Fri, 25 May 2007 13:36:16 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705251332360.4648@racer.site> (raw)
In-Reply-To: <f36g7l$2oe$1@sea.gmane.org>
Hi,
On Fri, 25 May 2007, Jakub Narebski wrote:
> Johannes Schindelin wrote:
>
> > Hi,
> >
> > On Thu, 24 May 2007, Panagiotis Issaris wrote:
> >
> >> So, we're asking for /ffmpeg/info/refs, and the server is returning
> >> c30fa8391812..., but, using GitWeb one can see that c30fa839812... is
> >> not the last commit, this one is:
> >> http://git.mplayerhq.hu/?p=ffmpeg;a=commit;
> >> h=47d7dcb5a7d89f413064e7ef1b54d77e59fb8375
> >
> > 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.
>
> If you push to repository (it is the usual setup for public
> repositories), it would be enough to simply enable default
> 'post-update' hook (make it executable).
>
> If you however for example commit to this public repository directly,
> you would need to put call to git-update-server-info in the 'post-commit'
> hook.
I have the slight suspicion that this repo is only updated via git-svn.
And I am still new enough to git-svn to not know which hook it executes,
if any.
Ciao,
Dscho
prev parent reply other threads:[~2007-05-25 12:36 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
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 [this message]
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=Pine.LNX.4.64.0705251332360.4648@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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).