Sharpen doc for min/max _ind functions

[jo-37]

No description provided.

[coveralls]

coverage: 32.752% (-0.008%) from 32.76%
when pulling 07c3431 on jo-37:contrib
into a8400e6 on PDLPorters:master.

[mohawk2]

Please don't create multiple PRs for one change. You could just have force-pushed your contrib branch rather than close and open a new one.

[mohawk2]

Thanks for these!

[jo-37]

Please don't create multiple PRs for one change. You could just have force-pushed your contrib branch rather than close and open a new one.

Sorry, I don't understand. I accidentally pushed to a branch that was not completely merged. To avoid a total mess, I closed the PR and opened a new one. Though I'm not a complete git noob, I don't know how I could have done better.

[mohawk2]

Pushing to a branch doesn't create a PR. A preferred option would have been to leave it open but mark it as "draft" (there's a button).

[jo-37]

On Sun 02 Jun 2024 04:12:46 PM CEST, mohawk2 ***@***.***> wrote: Pushing to a branch doesn't create a PR. A preferred option would have been to leave it open but mark it as "draft" (there's a button).

Confused. Created a PR from a fresh branch. I don't see anything wrong here.

…

-jo

[mohawk2]

Yes, I can see that you don't. The next time you open a PR by accident, please don't immediately close it, instead ask for advice. It is untidy and unnecessary to fire through more than one PR per intended change, and it's fine to just mark one as draft (so it can't be merged) if more needs doing.