How to fix bugs

Marcel Pol mpol at gmx.net
Sat Sep 25 00:13:17 UTC 2004


On Fri, 2004-09-24 at 21:15 +0200, Roland Illig wrote:
> what is the usual workflow of fixing a bug? Today I added the patches 
> from the OpenBSD project and fixed a bug that had been reported in the 
> Redhat BTS.
> 
> So how are we going to inform the package maintainers (for Debian, 
> NetBSD, OpenBSD, FreeBSD, Redhat) that their bugs are closed, their 
> patches applied?

It should be the other way around. If downstream has patches then they
should send it upstream if it's appropriate. Then when upstream does a
new release the patches will give failed hunks, or ask for reverse
patching. Mostly that's enough notice (imo) and patches can then be
dropped or regenerated by downstream.

If there are open bugs for which you make patches then it would be very
polite to notify them. Imo it's not necessary, and I think it can be a
lot of effort to check every downstream bugzilla. 

-- 
Marcel Pol




More information about the mc-devel mailing list