Re:Commit messages guide
by andreareina on Saturday April 20, 2019 @12:43AM
(#19704844)
Maximum flexibility with minimum complexity. You want lines that wrap because humans are going to read the message. But you need to be able to not wrap when needed, e.g. when posting code snippets. You need something that any client (including email clients written 10 years before git was a thing) is going to recognize and know how to display correctly. Hard-wrapped plain text fits the bill.
[ Parent
| on HN ]
Why would you need to support a commit message in a 10 year old client? This is like saying you need to support IE8 in a web app. If the person doesn't like things being broken, then maybe they should update there software...
Re:Commit messages guide
by intertextuality on Saturday April 20, 2019 @06:20AM
(#19705722)
> 10 year old client
Or simply using a terminal with multiple windows open. I hard wrap at 50 chars and I haven't died from exertion yet.
The ability to display commit messages nicely probably is not the metric by which people chose their email client.
Wrapping text where it makes sense is also a task which is best done by the human writing it.
I'd rather have a meaningful text flow with sense than some machine hard wrapping in the mi
dle of the
sentence.