[bug #66568] document whether find's -execdir option is guaranteed to produce pathnames that start with ./

Follow-up Comment #4, bug #66568 (group findutils): Thanks for merging. I think it would be good if the status of `/` in -execdir could be clarified before a release is made with my documentation patch, because now we in principle "promise" that it's the way as documented and people may actually

[PATCH] maint: pull in gnulib module basename-lgpl

* bootstrap.conf (gnulib_modules): Add 'basename-lgpl', because we're using the gnulib 'base_name' function. --- bootstrap.conf | 1 + 1 file changed, 1 insertion(+) diff --git a/bootstrap.conf b/bootstrap.conf index bfd84141..2485e2ab 100644 --- a/bootstrap.conf +++ b/bootstrap.conf @@ -76,6 +76

[bug #66568] document whether find's -execdir option is guaranteed to produce pathnames that start with ./

Update of bug #66568 (group findutils): Status: Confirmed => Fixed Fixed Release:None => 4.11.0 ___ Follow-up Comment #3: Thanks - pushed with some minor tweaks, e.g. the commi

[bug #46791] wishlist: no option to find devices for major/minor

Follow-up Comment #4, bug #46791 (group findutils): That debian bug report is 18 years old and didn't get much love. You could instead use my rawhide (rh) program (an alternative to find(1)). It is mentioned in the debian bug report you refer to. rh can include major/minor device numbers in its s