From: "Mike Ralphson" <mike.ralphson@gmail.com>
To: "Frank Lichtenheld" <frank@lichtenheld.de>
Cc: "Geoffrey Ferrari" <geoffrey.ferrari@googlemail.com>,
git@vger.kernel.org
Subject: Re: Post-update hook problems
Date: Fri, 5 Oct 2007 13:27:17 +0100 [thread overview]
Message-ID: <e2b179460710050527w185fd4b1kfbe278cf7055de4c@mail.gmail.com> (raw)
In-Reply-To: <20071005120850.GM31659@planck.djpig.de>
On 10/5/07, Frank Lichtenheld <frank@lichtenheld.de> wrote:
> On Fri, Oct 05, 2007 at 12:27:22PM +0100, Geoffrey Ferrari wrote:
> > --
> > fatal: Not a git repository: '.'
> > Failed to find a valid git directory.
> > --
> >
> > Can anyone explain why this happens? And how can I make the script
> > work properly?
>
> I'm no hook expert, but it may have something to do with some
> environment variables that are set in hooks, you might need to change
> variables like GIT_DIR.
Ack.
The hooks seem to assume repositories pushed into are bare, so the
GIT_DIR isn't set to a .git subdirectory (even if it exists).
Mike
prev parent reply other threads:[~2007-10-05 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 11:27 Post-update hook problems Geoffrey Ferrari
2007-10-05 12:08 ` Frank Lichtenheld
2007-10-05 12:27 ` Mike Ralphson [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=e2b179460710050527w185fd4b1kfbe278cf7055de4c@mail.gmail.com \
--to=mike.ralphson@gmail.com \
--cc=frank@lichtenheld.de \
--cc=geoffrey.ferrari@googlemail.com \
--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).