Re: Dropping core.worktree and GIT_WORK_TREE support

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 25, 2008, 03:05 UTC
Message-ID: <7v1w0dkd5s.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <20080825020054.GP23800@genesis.frugalware.org>

Miklos Vajna <vmiklos@frugalware.org> writes:

Show 7 quoted lines

> On Sun, Aug 24, 2008 at 05:30:54PM -0700, Junio C Hamano <gitster@pobox.com> wrote:
>> Heh, if we are to do the attention-getter, let's do so more strongly ;-)
>
> Does this include removing of --work-tree as well?
>
> The git backend of Pootle (http://translate.sourceforge.net/wiki/) uses
> it.

Interesting. Does it use it because it can (meaning, --work-tree is supposed to work), or because --work-tree is the cleanest way to do what it wants to do (if the feature worked properly, that is, which is not the case)?

Show 14 quoted lines

> Also, here is a question:
>
> $ git --git-dir git/.git --work-tree git diff --stat|tail -n 1
>  1443 files changed, 0 insertions(+), 299668 deletions(-)
>
> So, it's like it thinks every file is removed.
>
> But then:
>
> $ cd git
> $ git diff --stat|wc -l
> 0
>
> is this a bug, or a user error?

I think it is among the many other things that falls into "the two attempts still haven't resolved" category.