[bug #20951] Very bad/unclear/confusing documentationing for a security note of find's -execdir option

[James Youngman]

Update of bug #20951 (project findutils):

                Severity:              3 - Normal => 2 - Minor              

    _______________________________________________________

Follow-up Comment #1:

I had written "current directory" because having an empty element or a
leading/trailing colon in $PATH has the same effect as ".".  This being the
case, I hadn't wanted to write "."

I now realise that the effect is less clear than I had hoped.  I will think
about how to make this clearer.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?20951>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/