all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 23769@debbugs.gnu.org, Noam Postavsky <npostavs@users.sourceforge.net>
Subject: bug#23769: 25.0.95; Mode Line breakage in vc-git
Date: Thu, 16 Jun 2016 08:11:50 +0100	[thread overview]
Message-ID: <87ziqlzjyh.fsf@russet.org.uk> (raw)
In-Reply-To: <87e22f3a-27d2-338e-05f7-b3ab820dbe5f@yandex.ru> (Dmitry Gutov's message of "Thu, 16 Jun 2016 02:20:53 +0300")

Dmitry Gutov <dgutov@yandex.ru> writes:

> On 06/16/2016 01:27 AM, Noam Postavsky wrote:
>
>> Apparently this "_the_ right way to write hooks that touch the files
>> in the work tree."
>>
>> http://permalink.gmane.org/gmane.comp.version-control.git/136276
>
> Is it the same behavior we're talking about?
>
> The thread says that GIT_DIR is set to '.', not to '.git'. I doubt the former
> setting would mesh well with binding default-directory to repository's root
> like the patch proposes.

According to this:

http://longair.net/blog/2011/04/09/missing-git-hooks-documentation/

that's for the post-recieve hook. In this case CWD is the git directory.
The logic of this is (I guess) that it works also in a bare repo.
pre-commit can only ever run in a non-bare repo since you cannot commit
if you don't have a worktree.

I suspect emacs will not be affected by this because if anyone did
run emacs in post-recieve they would only touch files *inside* the git
repo which Emacs would identify as not version-controlled.

But, again, it illustrates the point that GIT_DIR can (and is often) set
to a relative directory.

Phil






  reply	other threads:[~2016-06-16  7:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14 11:16 bug#23769: 25.0.95; Mode Line breakage in vc-git Phillip Lord
2016-06-14 16:29 ` Glenn Morris
2016-06-14 17:03   ` Phillip Lord
2016-06-14 21:52     ` Dmitry Gutov
2016-06-14 22:21       ` Phillip Lord
2016-06-15 20:48       ` Phillip Lord
2016-06-15 21:02         ` Dmitry Gutov
2016-06-15 22:09           ` Phillip Lord
2016-06-15 22:27             ` Noam Postavsky
2016-06-15 23:20               ` Dmitry Gutov
2016-06-16  7:11                 ` Phillip Lord [this message]
2016-06-16  7:45               ` Phillip Lord
2016-06-15 23:25             ` Dmitry Gutov
2016-06-16  7:41               ` Phillip Lord
2016-06-16 11:25                 ` Dmitry Gutov
2016-06-16 16:06                   ` Dmitry Gutov
2016-06-16 16:54                     ` Noam Postavsky
2016-06-16 16:59                       ` Dmitry Gutov
2016-06-16 21:47                       ` Phillip Lord
2016-06-16 22:13                         ` Dmitry Gutov
2016-06-16 22:23                           ` Phillip Lord
2016-06-16 22:31                             ` Dmitry Gutov
2016-06-16 22:42                               ` Phillip Lord
2016-06-17  2:41                                 ` Dmitry Gutov
2016-06-17  3:37                                   ` Noam Postavsky
2016-06-17  6:54                                     ` Eli Zaretskii
2016-06-17 12:06                                       ` Dmitry Gutov
2016-06-17 13:21                                         ` Eli Zaretskii
2016-06-17 13:54                                           ` Dmitry Gutov
2016-06-17 15:09                                         ` Phillip Lord
2016-06-16 21:47                     ` Phillip Lord
2016-06-16 22:04                       ` Dmitry Gutov
2016-06-21 16:46                         ` Dmitry Gutov
2016-06-21 20:45                           ` Phillip Lord
2016-06-21 23:06                             ` Dmitry Gutov
2016-06-15 21:56         ` John Wiegley
2016-06-14 21:30   ` Phillip Lord

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=87ziqlzjyh.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=23769@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=npostavs@users.sourceforge.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.