From: "Torsten Bögershausen" <tboegi@web.de>
To: Sebastian Feldmann <sf@sebastian-feldmann.info>, git@vger.kernel.org
Subject: Re: Impossible to change working directory
Date: Sat, 1 Oct 2016 17:34:05 +0200 [thread overview]
Message-ID: <477492a9-7ff2-59d0-1463-b47694ce66c1@web.de> (raw)
In-Reply-To: <A99D7D06-8214-4C09-BCB2-E4FCE75FF317@sebastian-feldmann.info>
On 29.09.16 21:30, Sebastian Feldmann wrote:
> Hi there,
>
> I have a problem executing a pre-commit hook.
> The hook script has to change the working directory to work and if I use plain
>
> git commit
>
> it works as expected, the script executes without errors, but if I use
>
> git commit —only file.x file.y
>
> the script fails because changing the current working directory fails.
> If I echo the current working directory it always echoes the root repository path
>
> Is this expected behavior?
> Thanks for your feedback.
Is there any chance to send us the content of the script ?
(Or a demo example, which doesn't work)
prev parent reply other threads:[~2016-10-01 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 19:30 Impossible to change working directory Sebastian Feldmann
2016-09-29 23:24 ` Junio C Hamano
2016-10-01 15:34 ` Torsten Bögershausen [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=477492a9-7ff2-59d0-1463-b47694ce66c1@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=sf@sebastian-feldmann.info \
/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