[debian-mysql] git commits and debian/changelog

Robie Basak robie.basak at canonical.com
Tue May 10 13:15:32 UTC 2016

Failed to copy the list, resending. Sorry!

On Mon, May 09, 2016 at 06:27:38PM +0200, Bjoern Boschman wrote:
> basically +1
> but I'd think that new pkg-mysql members might get confused?

I don't think it's too onerous to ask for good git commit messages with
no change to debian/changelog. New members should be seeking review
before pushing to VCS anyway, and it's trivial for a committer to drop
any debian/changelog before pushing.

> even though I am not sure if all commit msgs should be reflected in d/ch?

I don't think this needs to be a requirement. I'm happy for whoever
creates d/ch to tweak it at that time.

On Tue, May 10, 2016 at 07:23:32AM +0200, Lars Tangvald wrote:
> There's also the issue of bug references; we'd need to add them to the first
> line in the commit to get them included in the changelog, right?

gbp-dch seems to be clever here. I just tried adding a line "Closes:
#XXX, #YYY" to the end of my commit (the body, not the first line) and
gbp-dch picked them up and added them to the first line to generate the
changelog message. So I think we're OK here.


More information about the pkg-mysql-maint mailing list