https://bugzilla.novell.com/show_bug.cgi?id=823410 https://bugzilla.novell.com/show_bug.cgi?id=823410#c11 Egbert Eich <eich@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |eich@suse.com Resolution|FIXED | --- Comment #11 from Egbert Eich <eich@suse.com> 2013-06-07 07:23:50 UTC --- Guys, this is not the proper way to do it! We do *not* want to maintain a patch forever therefore we need to make sure that it becomes integrated in upstream or else not take it. The proper way to handle this is: 1. Find out if this patch has been posted to xorg-devel already, if there was a discussion and what the outcome was. If the outcome was to not bother with Xvfb any more then we should probably drop the idea. 2. In all other cases, preprare what was proposed. 3. If there was no discussion a. port the patch to the current git head b. add a commit message describing why this patch is useful c. attribute authorship to original author. 4. post it to xorg-devel (and Keith Packard personally). 5. make sure that the patch receives attention. Michal, would you have time to do this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.