On Dec 17, 2013, at 1:40 PM, jcar...@users.sourceforge.net wrote:
> The shell was failing to correctly parse up to the space only for
> ?\226?\128?\156run (1 3)?\226?\128?\157 and also losing the space for
> ?\226?\128?\156in ?\226?\128?\157 a b?\226?\128?\157 c?\226?\128?\157 for
> loop initialization. This fixes for initialization to be correct.
I see a lot of unreadable content in the commit messages is there some way to
automate a fix for this? It looks to me like the editor is inserting “LEFT
DOUBLE QUOTATION MARK” and “RIGHT DOUBLE QUOTATION MARK” and not QUOTATION
MARK. It basically looks like the email is getting UTF-8 characters, but trying
to print them as ASCII? That is why it seems like some kind of configuration
bug?
~/work/edk2/ShellPkg/Library/UefiShellLevel1CommandsLib>svn log For.c
------------------------------------------------------------------------
r14997 | jcarsey | 2013-12-17 13:40:41 -0800 (Tue, 17 Dec 2013) | 7 lines
ShellPkg: Fix "for" command statement initialization.
The shell was failing to correctly parse up to the space only for “run (1 3)”
and also losing the space for “in ” a b” c” for loop initialization. This
fixes for initialization to be correct.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jaben Carsey <jaben.car...@intel.com>
Thanks,
Andrew Fish
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
