Bcachefs kernel history: how to check an old merge prediction

An old prediction about when a filesystem would enter the kernel can be historically interesting and currently misleading.

Separate prediction from release

Write down the publication date of the claim and the kernel version it discussed. Then check the relevant release notes or official kernel documentation for that version. “Not in version X” is different from “never merged.” Avoid changing the tense of the original claim when citing it.

Check the current documentation

The kernel documentation has a bcachefs section. Read the documentation for the kernel version relevant to the system being discussed, because features and support can change. A guide for an older release should keep its version in the title or introduction. Back up data before experimenting with a filesystem and use the applicable project and distribution guidance.

Record the uncertainty

Distinguish documentation, release records, developer discussion and speculation. If you cannot verify a precise merge milestone from primary records, say so. For a production storage choice, evaluate support, recovery practice and the actual distribution instead of deciding from one historical blog headline.

Try it on a real case

A reader finds a 2023 headline about kernel 6.5. They note its date, open the kernel documentation for the version on their machine and check release records before drawing a conclusion about present support.

Limit: This is a history and verification guide, not a recommendation to migrate a live filesystem.