4 ms·
Markdown renderers seem perfectly capable of this. git wouldn't even need to disambiguate asterisk for lists vs. asterisk for emphasis.
by chris_7 10y ago
Markdown renderers seem perfectly capable of this. git wouldn't even need to disambiguate asterisk for lists vs. asterisk for emphasis.
- masklinn 10y agoSo every piece of software now needs a markdown renderer?
- chris_7 10y agoIf Linus wants a consistent commit message format, he should enforce it at the software level, rather than hoping people read a comment he left in a repository about logging his swimming information. This does not mean that the format needs to be Markdown (which includes embedded HTML, so obviously not Markdown), or that all software needs a Markdown renderer. I'm not sure why you'd conclude that.
- wruza 10y agoEnforcing is an administrative task committed by specific people in specific projects (there is a thing called 'best practice', but it never is a hard rule). Tools authors should not enforce anything, it's not their job, responsibility and competence, even if a particular project like Linux has the same Linus for both project management / rcs tool writing.
- Avshalom 10y agowe don't even need markdown. Groff and less are already there and already handle formatting and reflowing just fine.
- masklinn 10y agoGroff is a text processing/formatting system so same issue, and less doesn't handle jack shit.