David M Williams
2012-02-26 19:21:30 UTC
I have seen at least a few projects discussing if/how to "standardize"
their Git commit messages. Such as
GEF:
http://dev.eclipse.org/mhonarc/lists/gef-dev/msg01541.html
Platform-UI:
http://dev.eclipse.org/mhonarc/lists/platform-ui-dev/msg05180.html
There seems to be a healthy back-and-forth discussion of pros and cons of
various approaches in those chains of mailing list messages (with differing
conclusions, if I'm skim reading them right).
It is certainly within each project's "rights" to decide how their project
committers should do it, but ...
I could not help but wonder if there should not be a bit larger
"eclipse-wide" discussion of "how to do it", such as
on this list? Or, would "architecture council list" be better? (Is this
list for more technical Git migration discussions?)
Perhaps there would end-up being some "common, minimum recommendation" ...
even if projects embellished on that common one?
Perhaps a "common" git wiki page with that recommendation and/or with
pointers off to the more project-specific practices would help improve
quality of Eclipse commit logs?
I'd be the last person to think all projects need to do it exactly the same
way ... but, I think a bit broader discussion would be good, and a bit of
knowledge sharing might help projects make the best choice for themselves,
especially for those new and unfamiliar with Git?
If anyone agrees, what would be best list to have that common discussion?
Thanks,
their Git commit messages. Such as
GEF:
http://dev.eclipse.org/mhonarc/lists/gef-dev/msg01541.html
Platform-UI:
http://dev.eclipse.org/mhonarc/lists/platform-ui-dev/msg05180.html
There seems to be a healthy back-and-forth discussion of pros and cons of
various approaches in those chains of mailing list messages (with differing
conclusions, if I'm skim reading them right).
It is certainly within each project's "rights" to decide how their project
committers should do it, but ...
I could not help but wonder if there should not be a bit larger
"eclipse-wide" discussion of "how to do it", such as
on this list? Or, would "architecture council list" be better? (Is this
list for more technical Git migration discussions?)
Perhaps there would end-up being some "common, minimum recommendation" ...
even if projects embellished on that common one?
Perhaps a "common" git wiki page with that recommendation and/or with
pointers off to the more project-specific practices would help improve
quality of Eclipse commit logs?
I'd be the last person to think all projects need to do it exactly the same
way ... but, I think a bit broader discussion would be good, and a bit of
knowledge sharing might help projects make the best choice for themselves,
especially for those new and unfamiliar with Git?
If anyone agrees, what would be best list to have that common discussion?
Thanks,