Comment 6 for bug 591847

Thanks for your contribution! I've just sponsored it into Natty. I edited the changelog to re-target the upload to natty instead of maverick, and I added the fields from the Debian Patch Tagging Guidelines (http://dep.debian.net/deps/dep3/) so we can more easily keep track of the patch. Other than that the patch looked good.

I've also submitted the patch to Debian using the submittodebian tool in ubuntu-dev-tools. This is something that you can do yourself in the future. Especially for packages where the Debian maintainers are responsive (which is especially common for packages maintained by a team) and where there aren't already Ubuntu-specific changes, submitting patches to Debian can be the fastest way to get changes in.

Also, when you have a debdiff that's ready to be uploaded, you should subscribe ubuntu-sponsors (as per https://wiki.ubuntu.com/SponsorshipProcess). That will make sure that the patch gets in front of Ubuntu sponsors so it can be handled more quickly on our side.