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

On Fri, 2007-09-07 at 13:43 -0700, Junio C Hamano wrote:
> "Josh England" <jjengla@sandia.gov> writes:
> 
> > In messsing around with hooks, I've discovered that not all hooks are
> > run in the same environment.  In particular, the current working
> > directory in the post-receive hook (maybe others as well) is the GIT_DIR
> > (.git) directory, instead of the root of the working tree (as in
> > pre-commit).
> 
> It is not even "instead of"; that's the only sane thing to do
> for post-receive, which is in response to git-push and usually
> used for a bare repository, i.e. without any work tree.

I thought there was probably a sane reason for it.  That is perfectly
acceptable, but the problem still exists that 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.

-JE

  reply	other threads:[~2007-09-07 21:26 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 [this message]
2007-09-07 21:44     ` Junio C Hamano
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

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

  git send-email \
    --in-reply-to=1189200421.12525.8.camel@beauty \
    --to=jjengla@comcast.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.