git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: evgeny <illumsoft.org@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: t0005-signals.sh fails with ksh
Date: Sat, 9 May 2015 02:43:00 +0300	[thread overview]
Message-ID: <479525721.20150509024300@gmail.com> (raw)
In-Reply-To: <xmqqk2wiiwa3.fsf@gitster.dls.corp.google.com>

Hi,
just for information about ksh on Linux and OpenIndiana

           ksh93 on Debian GNU/Linux 7 (wheezy)

$ ksh --version
  version         sh (AT&T Research) 93u+ 2012-02-29

$ git init foo && cd foo
Initialized empty Git repository in /var/tmp/foo/.git/
$ (cd .git/objects && ls)
info  pack
$ mkdir subdir && cd subdir
$ ls ../.git/objects
info  pack
$ cd ../.git/objects
/bin/ksh93: cd: /var/tmp/foo/git/objects: [No such file or directory]


           ksh93 on OpenIndiana oi_151.1.9 X86

$ ksh --version
  version         sh (AT&T Research) 93t+ 2010-03-05

$ pwd
/var/tmp
$ git init foo && cd foo
Initialized empty Git repository in /var/tmp/foo/.git/
$ (cd .git/objects && ls)
info  pack
$ mkdir subdir && cd subdir
$ ls ../.git/objects
info  pack
$ cd ../.git/objects
$ pwd
/var/tmp/foo/.git/objects

Looks like older version (or Solaris version?) of ksh did not have this bug.

Saturday, May 9, 2015, 12:39:32 AM, you wrote:

> 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.





-- 
Best regards,
 evgeny                            mailto:illumsoft.org@gmail.com

  reply	other threads:[~2015-05-08 23:36 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
2015-05-08 23:43         ` evgeny [this message]
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=479525721.20150509024300@gmail.com \
    --to=illumsoft.org@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).