Commit messages

[Dustin Kirkland]

On Jan 20, 2016 5:08 PM, "Oliver Grawert" <ogra at ubuntu.com> wrote:
>
> hi,
> Am Mittwoch, den 20.01.2016, 18:53 -0200 schrieb Gustavo Niemeyer:
>
> > So, for the actual proposal. My initial recommendation would be the
> > following format:
> >
> > """
> > <affected packages>: <summary in lowercased imperative mood ("add",
> > not "added"), no full stop>
> >
> > <description with prose in proper English>
> >
> > {Closes,Updates} #<bug number>[,<bug number>]
> > """
> >
> > A more concrete example:
> >
> > """
> > asserts,daemon,cmd/snap: introduce "asserts" subcommand
> >
> > New "asserts" subcommand allows querying the database of known
> > assertions.
> >
> > Updates #123456,782345
> > Closes #415211
> > """
> >
>
> would it be possible to have a script or some such that also generates
> a proper debian/changelog file with the corresponding "LP: #XXXXXXX"
> entries from the commits ?

Check out the bch command in the bikeshed package/project for inspiration.
It does exactly that and we've used it for hundreds of packages/projects
over the last 5 years.

http://manpg.es/bch

> currently mvo creates the package by hand and we end up with changelog
> entries like "* new git snapshot", so neither the launchpad bugs get
> auto-closed nor can you see the actual list of changes in the package
> changelog (i understand it is painful to transfer git commit summaries
> by hand for each package upload, if we had a file you could just
> copy/paste from that might be helpful in this case)
>
> ciao
>         oli
>
> --
> snappy-devel mailing list
> snappy-devel at lists.ubuntu.com
> Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snappy-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snappy-devel/attachments/20160121/2fee804c/attachment.html>