On Sun, Jan 28, 2018 at 6:57 PM Bernhard Voelker
wrote:
> On 01/27/2018 06:45 PM, Peng Yu wrote:
> >> glusterfs doesn't provide D_TYPE information:
> >>
> >> getdents(4, {{d_ino=10054722685526780333, ..., d_type=DT_UNKNOWN} ...
> >>
> >> Nevertheless, it is strange that find calls newfstatat() al
Follow-up Comment #8, bug #46815 (project findutils):
The existing behaviour is user-surprising.
POSIX specifies nly (IIRC) the rouding behaviour when dealing with sizes
lacking a suffix (i.e. implicitly, blocks). GNU find's current behaviour
generalizes this rounding behaviour, but many people
Update of bug #40706 (project findutils):
Status:None => Works For Me
Assigned to:None => jay
Open/Closed:Open => Closed
Update of bug #36763 (project findutils):
Status:None => Fixed
___
Follow-up Comment #1:
I updated the Texinfo and manpage. See attached patch (which is already
applied in git head)
Update of bug #36763 (project findutils):
Assigned to:None => jay
___
Additional Item Attachment:
File name: 0001-doc-don-t-mention-indirect-blocks.-Clarify-how-size-.patch
Size:2 KB
Update of bug #26885 (project findutils):
Assigned to:None => jay
Open/Closed:Open => Closed
___
Follow-up Comment #9:
Closing due to la
Something I haven't heard explained on this thread yet is why the
change would be worthwhile in terms of cost (to e.g. the GNU project)
vs. benefit (to e.g. users).
The cost is, I hope, reasonably obvious:
- the maintenance burden of the extra code and maintaining both
fork/exec and posix_spawn i
Follow-up Comment #2, bug #54634 (project findutils):
I applied the attached patch in order to make things a bit clearer (I think).
(file #45077)
___
Additional Item Attachment:
File name: 0001-README-refer-user-to-README-hacking-when-ther
Update of bug #54667 (project findutils):
Status:None => Invalid
Open/Closed:Open => Closed
___
Follow-up Comment #4:
As far as I can s