Hi Alex, Getting back to the fanotify man page backlog... > > > > > We have a rather long backlog of man page updates pending merge > > from Matthew, Gabriel and myself. > > We need to merge them by order. > > The entire stack is available in [BRANCHES] on my github tree [1]. > > > > Let me summarize it for you again: > > Thanks. I'll write here what I know about the, just to be sure I didn't > miss anything. If you need anything from me, please tell me. > > > > > FAN_REPORT_PIDFD v5.15 [fanotify_pidfd] I see you finally managed to flow this into kernel.org repo. Yay! :) > > Pending a rewording of a paragraph. > > > FAN_FS_ERROR v5.16 [fan-fs-error] > > This one. Looks good to me. > Rebased on top of upstream, fixed the few minor nits you pointed out and push to: https://github.com/amir73il/man-pages/commits/fan-fs-error Can you please apply? > > FAN_REPORT_TARGET_FID v5.17 [fanotify_target_fid] > > I don't see this one in my mbox or linux-man@. > I assume it's not yet ready? > > > FAN_RENAME v5.17 [fan_rename] > > I don't see this either. I assume it's not ready either. > And now I can finally proceed to post these :) > > > > And I have more changes for upcoming v5.19... > I have a question for you regarding new UAPI, such as FAN_MARK_EVICTABLE that got merged to v5.19-rc1. Often, Michael would not want to merge UAPI changes to man pages before .0 release, because UAPI changes could be reverted before final release (which happened for fanotify). I still want to post those man page patches for review early, but don't want to mess up your patch review process. I guess if I post them as [RFC] it will be a good sign for you not to merge them until the .0 release? Should I simply use the subject "Fanotify updated for v5.19"? Do you have a different view on the matter? Don't care at all? ;-) Thanks, Amir.
