From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: evgeny <illumsoft.org@gmail.com>, git@vger.kernel.org
Subject: Re: t0005-signals.sh fails with ksh
Date: Fri, 08 May 2015 14:39:32 -0700 [thread overview]
Message-ID: <xmqqk2wiiwa3.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150508211453.GA11594@peff.net> (Jeff King's message of "Fri, 8 May 2015 17:14:54 -0400")
Jeff King <peff@peff.net> writes:
> 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.
next prev parent reply other threads:[~2015-05-08 21:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 20:15 t0005-signals.sh fails with ksh evgeny
2015-05-08 20:34 ` Junio C Hamano
2015-05-08 20:55 ` Jeff King
2015-05-08 21:14 ` Jeff King
2015-05-08 21:39 ` Junio C Hamano [this message]
2015-05-08 23:43 ` evgeny
2015-05-09 8:20 ` Andreas Schwab
2015-05-08 21:16 ` Junio C Hamano
2015-05-08 21:21 ` Jeff King
2015-05-09 20:01 ` brian m. carlson
2015-05-08 23:05 ` evgeny
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=xmqqk2wiiwa3.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=illumsoft.org@gmail.com \
--cc=peff@peff.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.
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.