From: "Carsey, Jaben" <jaben.carsey@intel.com>
To: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH 0/3] Update CWD and current mapping properly
Date: Tue, 29 Aug 2017 14:58:39 +0000 [thread overview]
Message-ID: <CB6E33457884FA40993F35157061515C752D3622@FMSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <20170829081107.442452-1-ruiyu.ni@intel.com>
Series.
Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Ruiyu
> Ni
> Sent: Tuesday, August 29, 2017 1:11 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] [PATCH 0/3] Update CWD and current mapping properly
> Importance: High
>
> The patches fix several bugs that caused by not updating CWD and current
> mapping properly.
>
> Huajing Li (3):
> ShellPkg: Rename gShellCurDir to gShellCurMapping
> ShellPkg: Fix bug that fails to change CWD after "map -r".
> ShellPkg: Update CWD and current mapping when commands return
>
> ShellPkg/Application/Shell/Shell.c | 18 +++++++++-
> ShellPkg/Application/Shell/ShellProtocol.c | 8 ++---
> ShellPkg/Include/Library/ShellCommandLib.h | 4 +--
> .../UefiShellCommandLib/UefiShellCommandLib.c | 42
> +++++++++++++++++++---
> 4 files changed, 61 insertions(+), 11 deletions(-)
>
> --
> 2.12.2.windows.2
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-08-29 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 8:11 [PATCH 0/3] Update CWD and current mapping properly Ruiyu Ni
2017-08-29 8:11 ` [PATCH 1/3] ShellPkg: Rename gShellCurDir to gShellCurMapping Ruiyu Ni
2017-08-29 8:11 ` [PATCH 2/3] ShellPkg: Fix bug that fails to change CWD after "map -r" Ruiyu Ni
2017-08-29 8:11 ` [PATCH 3/3] ShellPkg: Update CWD and current mapping when commands return Ruiyu Ni
2017-08-29 14:58 ` Carsey, Jaben [this message]
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=CB6E33457884FA40993F35157061515C752D3622@FMSMSX103.amr.corp.intel.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