From: "Alcantara, Paulo" <paulo.alc.cavalcanti@hp.com>
To: "Cohen, Eugene" <eugene@hp.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Carsey,
Jaben <jaben.carsey@intel.com> (jaben.carsey@intel.com)"
<jaben.carsey@intel.com>
Cc: "Thompson, Mark L. (Boise IPG)" <mark.l.thompson@hp.com>
Subject: Re: Shell Path Issues with "../.."
Date: Wed, 3 Aug 2016 19:26:36 +0000 [thread overview]
Message-ID: <CS1PR84MB0230B81FBE86FB3EF7B6E057AC060@CS1PR84MB0230.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <AT5PR84MB02911C10CD11575F8FE7C6DBB4060@AT5PR84MB0291.NAMPRD84.PROD.OUTLOOK.COM>
Hi Eugene,
I think it has been fixed on master already. See the commit below:
commit 85df61243cb56c3d9c52a5005e65c4ea8bf60e52
Author: Qiu Shumin <shumin.qiu@intel.com>
Date: Tue Jun 21 16:18:56 2016 +0800
MdePkg: Fix 'cd ..\..' go up only 1 level.
When we try to cd up two levels using the "../.." notation we
only go up one level. This patch fix this bug.
Thanks,
Paulo
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Cohen, Eugene
Sent: quarta-feira, 3 de agosto de 2016 16:17
To: edk2-devel@lists.01.org; Carsey, Jaben <jaben.carsey@intel.com> (jaben.carsey@intel.com) <jaben.carsey@intel.com>
Cc: Thompson, Mark L. (Boise IPG) <mark.l.thompson@hp.com>
Subject: Re: [edk2] Shell Path Issues with "../.."
Reminder (a few months later)
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Cohen, Eugene
> Sent: Wednesday, March 30, 2016 4:51 PM
> To: edk2-devel@lists.01.org
> Cc: Thompson, Mark L. (Boise IPG) <mark.l.thompson@hp.com>
> Subject: [edk2] Shell Path Issues with "../.."
>
> Dear ShellPkg maintainer,
>
> We're seeing some weird stuff related to '..' in the shell.
>
> The issue is that when we try to cd up two levels using the "../.."
> notation we only go up one level:
>
> FS0:\dir1\dir2\dir3\>
> FS0:\dir1\dir2\dir3\> cd ..\..
> FS0:\dir1\dir2\>
>
> The same issue occurs using forward and back slashes. The old (EDK)
> shell used to handle this correctly.
>
> Any ideas what's going on here?
>
> Thanks,
>
> Eugene
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2016-08-03 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AT5PR84MB02912C0A878075AC54538DA2B4980@AT5PR84MB0291.NAMPRD84.PROD.OUTLOOK.COM>
2016-08-03 19:17 ` Shell Path Issues with "../.." Cohen, Eugene
2016-08-03 19:26 ` Alcantara, Paulo [this message]
2016-08-03 19:44 ` Cohen, Eugene
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-list 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=CS1PR84MB0230B81FBE86FB3EF7B6E057AC060@CS1PR84MB0230.NAMPRD84.PROD.OUTLOOK.COM \
--to=devel@edk2.groups.io \
/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