Re: t0005-signals.sh fails with ksh

From: Junio C Hamano <gitster@pobox.com>
Date: May 8, 2015, 21:39 UTC
Message-ID: <xmqqk2wiiwa3.fsf@gitster.dls.corp.google.com>
In-Reply-To: <20150508211453.GA11594@peff.net>

Jeff King <peff@peff.net> writes:

Show 17 quoted lines

> Here's an oddity I isolated based on a failure in t5502:
>
>   $ git init foo && cd foo
>   Initialized empty Git repository in /home/peff/foo/.git/
>
>   $ (cd .git/objects && ls)
>   info pack
>
> OK, makes sense. Now...
>
>   $ mkdir subdir && cd subdir
>   $ ls ../.git/objects
>   info  pack
>   $ cd ../.git/objects
>   ksh: cd: /home/peff/foo/git/objects: [No such file or directory]
>
> Um, what? Apparently using "../.foo" will eat the "." off of "foo"?

That is fun.  And doing

    $ mkdir -p git/objects

just before you create and chdir into subdir does tell me that the last "cd ../.git/objects" is turned into "cd ../git/objects".

Actually, with that extra thing, changing the last one to

    $ cd ../..git/objects

still takes me to ../git/objects, it seems.  But lookie here:

    $ cd ../.....git/objects
    ksh: cd: /var/tmp/x/ksh/...git/objects: [No such file or directory]

WAT.

I am tempted to say that we should write it off as utterly broken.