git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Teemu Likonen <tlikonen@iki.fi>
To: git@vger.kernel.org
Subject: Possible bug: hooks/post-update does not trigger
Date: Sat, 17 May 2008 18:28:16 +0300	[thread overview]
Message-ID: <20080517152816.GA23308@mithlond.arda.local> (raw)

Sort of a problem is that hooks/post-update script is never triggered.
I have the following setup:

I work on a local repository and publish my changes by pushing them into
a bare repository which lies on the same filesystem. The actual
publishing will then require "git update-server-info" and rsync'ing the
bare repository to another host which in turn serves the repo via http.
(No git installed on the remote side and probably never will.)

I want to make this process automatical and I have actually done it
already with hooks/post-receive. It works fine. I'm just wondering why
hooks/post-update doesn't work.

The default hooks/post-update contains the line

  exec git-update-server-info

So the file is sort of advertised being the "official" way of running
git-update-server-info. The problem is that on my bare repository side
that file never gets executed (yes, execute bits are on). I tried to put
"echo" and "touch stampfile" type commands there but nothing happens.

Well, my problem was solved simply by using hooks/post-receive instead.
I put the following lines there and it works great:

  git update-server-info
  rsync --recursive --delete . remotehost:public_html/repo.git

Still I'd like to know if there is a bug in hooks/post-update triggering
mechanism or did I do something wrong?

                 reply	other threads:[~2008-05-17 15:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080517152816.GA23308@mithlond.arda.local \
    --to=tlikonen@iki.fi \
    --cc=git@vger.kernel.org \
    /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).