r12125 - /desktop/unstable/vte/debian/changelog
Loïc Minier
lool at dooz.org
Sat Jul 28 19:50:49 UTC 2007
On Sat, Jul 28, 2007, alanbach-guest at users.alioth.debian.org wrote:
> * New upstream release, Closes: #421320, #418699
> + * New upstream release, Closes: #421320, #418699
Don't close real bugs with "new upstream release"; the only bugs you
may close with "new upstream release" are the one _requesting_ the new
upstream release. Here you should have:
* New upstream release.
- Fixes rendering of line-drawing characters; closes: #421320;
#418699.
(This is covered in new maintainer guides and/or developer reference.)
Please fix the changelog accordingly.
On Sat, Jul 28, 2007, alanbach-guest at users.alioth.debian.org wrote:
> * Dropped 60_fix-ctrl-dash.patch, merged upstream
On Sat, Jul 28, 2007, alanbach-guest at users.alioth.debian.org wrote:
> * Dropped 62_alt-arrows.patch, merged upstream
Please do these changes in the *same commit* as the new upstream
release when possible. The same remark goes for the changelog. You
did this change as part of the "new upstream release" change, so you
could write:
* New upstream release.
- Drop patches 60_fix-ctrl-dash, 62_alt-arrows; merged upstream.
It's particularly important to try to ensure that a SVN checkout is
always buildable (it wasn't between the "new upstream release" commit
and the second patch removal), especially because some autobuilder are
building the SVN automatically, and these may well try the intermediate
revisions and fail. But I'm sure you'll find it natural to group such
changes in the same commit as they belong together.
Thanks!
--
Loïc Minier
More information about the pkg-gnome-maintainers
mailing list