ps.1: Note change in default selection of current user's processes

[ziaee]

I think the best is when the usage change and the doc change are the same commit.

[olce]

In D49620#1131209, @ziaee wrote:

I think the best is when the usage change and the doc change are the same commit.

I can certainly see why. The trick is that the code and doc changes may call for different reviewers, and then some people would validate only the doc change, or only the code change, or both, without the precise scope being clear, which adds management complexity. So I'm not sure... except perhaps for small changes.

[olce]

Also, as you probably have noticed, the main manual page change is D49605, and all other changes are updates after code changes. The latter consist in slight changes/additions, and usually a bunch of deletions in the BUGS section and changes in the STANDARDS one.

[ziaee]

What we historically do is tagging manpages, and then someone will accept it as manpages.

[olce]

• Update the base (impacts of changes earlier in the series)

[olce]

(This change will be merged with the code change in D49619 on commit.)