@asiciliano, based on the review from @pauamma_gundo.com and @bcr, this is ready to be pushed whenever you are ready.

@asiciliano, based on the review from @bcr, this is ready to be pushed whenever you are ready.

@asiciliano, based on the review from @pauamma_gundo.com and @bcr, this is ready to be pushed whenever you are ready.

@asiciliano, based on the review from @pauamma_gundo.com and @carlavilla, this is ready to be pushed whenever you are ready.

Looks good to me.

Remove errant blank line

Remove a errant blank line

There is some other formatting that looks a bit off in the commit message. Harald, have a look at the commit template: https://docs.freebsd.org/en/articles/committers-guide/#git-mini-primer-getting-started

This clearly isn't helpful for anyone.

I'm unsure what happened to the link to the POSIX specification in that quoted post. In any case, it's https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/utilities/cp.html.

I read the part of the specification you quoted several times.

The build is failing because configure is unhappy with the bootstrap version.

configure: Found potential Boot JDK using configure arguments
configure: Potential Boot JDK found at /usr/local/openjdk23 is incorrect JDK version (openjdk version "23.0.2" 2025-01-21 OpenJDK Runtime Environment (build 23.0.2+7-2) OpenJDK 64-Bit Server VM (build 23.0.2+7-2, mixed mode, sharing)); ignoring
configure: (Your Boot JDK version must be one of: 24 25)
configure: error: The path given by --with-boot-jdk does not contain a valid Boot JDK
configure exiting with result code 1

We need an entry in java/Makefile.

In D53302#1217406, @emaste wrote:

In D53302#1217404, @emaste wrote:

Example in commit message needs a line break: touch foo cp -P foo bar

Your update and this comment crossed paths...

In D53302#1217404, @emaste wrote:

Example in commit message needs a line break: touch foo cp -P foo bar

In D53262#1217195, @mark_freebsdfoundation.org wrote:

Grammatically it's incorrect.

Sure. That's why I listed it as an optional suggestion. Your grammar checker must also say the first sentence is wrong because it's the same situation.

Add new entries and do some slight reorganization. The title was changed to accommodate git arc.

@freebsd_ny-central.org, I had to add a few more entries to the index as part of my testing of Foundation entries. Can I either add them here, or can you commit this so I can add them after your commit?

Sorry, I missed that you already added pkg-message.in. Looks good.

A pkg message for upgrades would also be helpful. People tend not to go out of their way to read UPDATING, but they might read a note when they do the package upgrade.

lgtm. It might be helpful to link to https://imapsync.lamiral.info/ChangeLog in the commit message so users can easily see what's changed since 2.290.

I rebased this on top of 5c22d5b7a120ba4aad20ebaf9a4d5492136f640c (java/openjdk11: honour MAKE_JOBS_NUMBER) and tested the build. It finished on main, but failed on 14.3.

Incorporate @emaste's suggestion.

@andrew, it will be the same situation as now, when we have to choose whether to list MFC candidates for stable/14 or stable/15 by default. If I understood our IRC conversation correctly, you requested mfc-candidates be updated to tell you your stable/15 MFC candidates by default. This change does that and will automatically do it for stable/16 as soon as stable/17 is tagged.

Add a comment before the git command that extracts the latest stable branch.