Hi Douglas, >> it's great that you provided modifications to the AppArmor profile in >> Debian! May I kindly ask you to send these upstream too?
>> If you think that's too much work, please just tag your bug using a >> usertag. The corresponding tag would be "merge-to-upstream" and then the >> AppArmor team can take care of this. See >> https://wiki.debian.org/AppArmor/Reportbug#Usertags for how to do that. > > Thanks. I am taking this last option because trying to work out where > that commit with the dots-for-spaces came from has baffled me, and in > dealing with upstream I lack the historical context of the two teams > interactions to know whether they would prefer the broken patch and > its fix merged into one or both in series or some other thing. People > are particular about how they like to manage mistakes in their git > trees, so it is best in this case that you/they do it. I've just updated the documentation: https://wiki.debian.org/AppArmor/Contribute/Upstream#Quick_howto_contribute_to_upstream_AppArmor_profiles_using_Git because I realized that some parts were missing. Basically the idea would always be to get patches upstreamed and then to tell Debian (Thunderbird + AppArmor) maintainers about it once it's been merged. For this particular case, I think Simon said he would take care of it. Have a nice day, ulrike
