docs: Clarify file name and path limitations (Issue #729)

[Roshana-R]

No description provided.

[geky-bot]

Tests passed ✓, Code: 17128 B (+0.0%), Stack: 1448 B (+0.0%), Structs: 812 B (+0.0%)

	Code	Stack	Structs		Coverage
Default	17128 B (+0.0%)	1448 B (+0.0%)	812 B (+0.0%)	Lines	2438/2599 lines (-0.0%)
Readonly	6234 B (+0.0%)	448 B (+0.0%)	812 B (+0.0%)	Branches	1288/1624 branches (-0.0%)
Threadsafe	17980 B (+0.0%)	1448 B (+0.0%)	820 B (+0.0%)		Benchmarks
Multiversion	17200 B (+0.0%)	1448 B (+0.0%)	816 B (+0.0%)	Readed	29000746676 B (+0.0%)
Migrate	18792 B (+0.0%)	1752 B (+0.0%)	816 B (+0.0%)	Proged	1482895246 B (+0.0%)
Error-asserts	17952 B (+0.0%)	1440 B (+0.0%)	812 B (+0.0%)	Erased	1568921600 B (+0.0%)

[BenBE]

AI slop?

[geky]

Oh huh, I think you're right.

I wasn't sure about this one, a lot of PRs have poor quality just because users are new to GitHub, but this is definitely not mergable. The diversity of PRs on their activity log, and lack of conversation/follow ups is telling though.

@Roshana-R Apologies if you're new to GitHub, unfortunately this antagonistic environment seems to be what Microsoft's GitHub wants to foster. Consider explaining your reasoning in future PRs if you're human.

[geky]

@BenBE I think both #1153 and #1152 are also AI slop. It's curious these were all opened roughly the same time.

[BenBE]

All of those PRs follow a similar pattern, and while the others aren't merge-able either, at least #1152 might have a chance if it were to be fixed. So that being said, the idea behind #1152 (replacing the LaTeX renders by proper Unicode text and internal Markdown formatting) looks sound.

[geky]

All of those PRs follow a similar pattern, and while the others aren't merge-able either, at least #1152 might have a chance if it were to be fixed. So that being said, the idea behind #1152 (replacing the LaTeX renders by proper Unicode text and internal Markdown formatting) looks sound.

You're right, but I'm happy to have an excuse to not change DESIGN.md right now.

Maybe I'm being a bad maintainer, but I'd like it if littlefs2's DESIGN.md could be frozen as-is, and any readability improvements moved to littlefs3's DESIGN.md (the part that makes me a bad maintainer is that littlefs3's DESIGN.md doesn't exist yet...).

GitHub's LaTeX is still a moving target, they have broken things and made me edit comments, and I'd hate if the last snapshot of littlefs2's DESIGN.md looks like:

$$\sum_i^n{(\operatorname{ctz}(i)+1)} = 2n-\operatorname{popcount}(n)$$

Just because GitHub decided to change things.

Though depending on how user's use littlefs2 vs littlefs3 when released, I may be being too farsighted.