[Bug 226529] Merge Review: vixie-cron

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Merge Review: vixie-cron


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=226529





------- Additional Comments From pertusus@xxxxxxx  2007-03-27 09:21 EST -------
Do you really mean that being able to associate a patch with a bug
is more important that being able to review the patches? That's
awfully wrong. And how do you coordinate with upstream or other
distros packagers if you have one patch per bug? Maintainability
is the most important consideration when it comes to patches
split management (as long as the final code is the same...).
Imagine one second that you leave this mess and somebody else
take over that package. How long will it take for the new maintainer
to understand the patches?

If you really want to associate a patch with a bug you can do 
some duplication (that is keep patches associated with a bug 
together with patch associated with features), either in the 
specfile, or on internet, but a readable patch must be there.

Given the level of disagreement, I guess that the only solution
is to escalate (first to the devel list and then we'll see) if you
don't reconsider your position.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

_______________________________________________
Fedora-package-review mailing list
Fedora-package-review@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-package-review

[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]