git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Josh England <jjengla@comcast.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: how to access working tree from .git dir?
Date: Fri, 07 Sep 2007 14:44:37 -0700	[thread overview]
Message-ID: <7vhcm62lru.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1189200421.12525.8.camel@beauty> (Josh England's message of "Fri, 07 Sep 2007 15:27:01 -0600")

Josh England <jjengla@comcast.net> writes:

> ... there doesn't seem to be a
> good way to access the top of the working tree from within the GIT_DIR.
> Since I now know that post-receive has a CWD in .git, I could just use
> `pwd`/../ , but I was hoping for a better (read: consistent between
> hooks) solution.

I do not think it is a bad thing for _your_ script to have the
knowledge that in _your_ repositories everywhere, the top of the
work tree is $GIT_DIR/.. and there is no repository that lacks a
work tree.  Obviously that would not work for people with bare
repositories, but they would not be using _your_ script in their
bare repositories, so that is Ok.

You can also configure core.worktree in $GIT_DIR/config and use
that from the hook script, I presume, although I haven't done it
(and do not see a need to do so) myself yet.

  reply	other threads:[~2007-09-07 21:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06 23:20 how to access working tree from .git dir? Josh England
2007-09-07 20:43 ` Junio C Hamano
2007-09-07 21:27   ` Josh England
2007-09-07 21:44     ` Junio C Hamano [this message]
2007-09-07 22:11       ` Josh England
2007-09-07 22:12         ` Junio C Hamano
2007-09-07 22:34           ` Josh England
2007-09-07 23:42             ` Junio C Hamano
2007-09-08  1:02               ` Josh England

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vhcm62lru.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jjengla@comcast.net \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).