Re: closing upstream bugs with debian/changelog
Scripsit Herbert Xu <email@example.com>
> I understand that you set yourself at a standard above the rest of us
> which is all good, but this is not how the majority of Debian developer
No matter how the majority of developers *do* operate, they all
*should* operate in a way that causes the bug log to contain an
explanation of why the developer closed it.
If one uses the changelog to close bugs, then that explanation must go
in the changelog. It's a simple as that.
> Besides, you can also provide the explanation by posting them to the
> BTS directly.
Which is excellent, but then there's no reason to use the changelog to
close the bug.
Henning Makholm "Det er du nok fandens ene om at
mene. For det ligger i Australien!"