On 27/06/10 12:07, Zhu, Peter J wrote:
Cool. I compared this with guideline and seem only missing or inconsistent
parts are a missing dash "-" between mail and version.
I wasn't explicit - I was just working on the link/bug refs so I knew what I was
looking at ;)
These:
# +- fix another two dialog transiences issues
# +-- bug#2393 (thanks to hao.h.li)
# +-- bug#1704
# +- fix l10n issue bug#1104
Really need to be "(BMC#1104)"
(of course, these are the guidelines as they stand at the moment).
I also (now) realise that the 'Message' in the update is not the same as the
changelog so it's just good luck that this still a valid example - sorry Michael ;)
Nb... whilst #1104 is pretty easy to spot, we should recognise that MeeGo-based
products will have MeeGo bugs co-existing with bugs in non-MeeGo packages and
bug managers. This means that a given release (and maybe even package) would
want to link to multiple bug-reporters.
Actually we have another tool of vc, that's part of packagint-tools, to
automatically to insert a new changelog entry into changesfile.
OK, thanks - we'll take a look at that.
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
