+1 Very good idea.<div> -Matthew Lye Leadership is responsibility, not privilege, Action, not position, Guidance, not knowledge, and outcome, not disposition. <No trees were harmed during this transmission. However, a great number of electrons were terribly inconvenienced> <div class="gmail_quote">On Tue, Oct 16, 2012 at 9:13 PM, Iain Lane <<a href="mailto:laney@ubuntu.com" target="_blank">laney@ubuntu.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi, A lot of our packages are patched over upstream. Each of these comes with a maintenance cost and is also a source of bugs and frustration (quilt patches aren't the easiest things in the world to work with). I think we should systematically look at our patches and re-evaluate for each one - Whether it is really (still) necessary — if not, drop - If we can forward upstream if not already or if we can help its upstream inclusion along - Who is going to maintain the patch in the distro if it needs to be kept as a local patch — desktop, PS, … It would be good if we could use something like DEP5 headers for all patches, including adding them to existing patches. It's sometimes really quite difficult to figure out what a particular patch is for, whether it is upstream and so on. Cheers, -- Iain Lane [ <a href="mailto:iain@orangesquash.org.uk">iain@orangesquash.org.uk</a> ] Debian Developer [ <a href="mailto:laney@debian.org">laney@debian.org</a> ] Ubuntu Developer [ <a href="mailto:laney@ubuntu.com">laney@ubuntu.com</a> ] -- ubuntu-desktop mailing list <a href="mailto:ubuntu-desktop@lists.ubuntu.com">ubuntu-desktop@lists.ubuntu.com</a> <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop</a> </blockquote></div> </div>