<div class="gmail_quote">On Thu, Dec 23, 2010 at 1:13 AM, Tim Bruijnzeels <span dir="ltr"><<a href="mailto:tim@ripe.net">tim@ripe.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">The - is still there so why is it now not seen as an argument?</div></blockquote><div><br></div><div>Because the dash is not at the start of the path.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">I still believe I should not have to worry about this though.</div></blockquote><div><br></div><div>Yeah, I am thinking that it would be good for rsync to protect filenames that start with a dash by putting a "./" in front of such names for the user. The only potential issue with doing that is that an advanced user may have taken advantage of this argument parsing to send options to the remote rsync (rather than using something like --rsync-path, or the upcoming --remote-option). I do also note that --protect-args didn't protect against dash interpretation like I was thinking that it did. I think I'll go ahead and commit such a change, since it makes basic functioning more rational.</div>
<div><br></div></div>..wayne..<br>