<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 31, 2015 at 8:08 AM, Laine Stump <span dir="ltr"><<a href="mailto:laine@laine.org" target="_blank">laine@laine.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="">On 01/20/2015 08:56 PM, David Lutterkort wrote:<br>
><br>
</span><span class="">> To make up for the extremely slow response, I opened a pull request<br>
> that hopefully addresses all this:<br>
> <a href="https://github.com/hercules-team/augeas/pull/198" target="_blank">https://github.com/hercules-team/augeas/pull/198</a><br>
><br>
> I'd highly appreciate review(s) of these patches as they root around<br>
> in some Augeas internals that shouldn't be disturbed ;)<br>
<br>
</span>During a review of netcf patches, Eric Blake has pointed out that the<br>
list of characters to escape should probably include the escape<br>
character itself ( \ ). Is this correct?<br></blockquote><div><br></div><div>Yes, that is correct since we want parse_name to be the inverse of pathx_escape_name  in pathx.c<br><br></div><div>After some surprising difficulty, I just pushed commit f7c2174e that addresses that.<br><br></div><div>David<br></div></div><br></div></div>