From: Jens Lehmann <Jens.Lehmann@web.de>
To: "Holding, Lawrence" <Lawrence.Holding@cubic.com>
Cc: git@vger.kernel.org,
Christian Hammerl <info@christian-hammerl.de>,
Antony Male <antony.male@gmail.com>
Subject: Re: Annoying absolute path for "core.worktree" to submodule
Date: Wed, 21 Mar 2012 20:41:43 +0100 [thread overview]
Message-ID: <4F6A2EF7.5090007@web.de> (raw)
In-Reply-To: <A5E8E180685CEF45AB9E737A010799802D9872@cdnz-ex1.corp.cubic.cub>
Am 20.03.2012 22:39, schrieb Holding, Lawrence:
> Slightly off topic, but related, what is the recommended way for finding
> the git folder from the top level project or any of the submodules?
Run "git rev-parse --git-dir" inside the repo whose git folder you want to
know.
> And of finding the working tree from inside a hook script?
I would expect hooks to be run in the work tree's top level directory,
but I haven't checked that.
next prev parent reply other threads:[~2012-03-21 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 9:52 Annoying absolute path for "core.worktree" to submodule Christian Hammerl
2012-03-20 13:31 ` Antony Male
2012-03-20 21:39 ` Holding, Lawrence
2012-03-21 19:41 ` Jens Lehmann [this message]
2012-03-21 9:42 ` Christian Hammerl
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=4F6A2EF7.5090007@web.de \
--to=jens.lehmann@web.de \
--cc=Lawrence.Holding@cubic.com \
--cc=antony.male@gmail.com \
--cc=git@vger.kernel.org \
--cc=info@christian-hammerl.de \
/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).