We've all been pretty lax about the amount of detail that we put in commit
messages some times, and I'd like to change that as we start Juno
development. Why? Well, just imagine that, six months from now, you're going
to write a document describing *all* the changes in Juno, just based on the
That seems to be reasonable to me.
Perhaps we should define a more or less formal format for commit
messages? That might
both help newcomers to write them make it easier for us to write
sensible What's changed
documents basing on those commit messages.
- Roman
On пн, 28-кві-2014 14:41:58
On 28/04/14 12:52, Roman Prykhodchenko wrote:
That seems to be reasonable to me.
Perhaps we should define a more or less formal format for commit
messages? That might
both help newcomers to write them make it easier for us to write
sensible What's changed
documents basing on those commit
