On 9/2/2014 14:53, Ron W wrote:
On Tue, Sep 2, 2014 at 2:35 PM, Warren Young <war...@etr-usa.com <mailto:war...@etr-usa.com>> wrote:(This is also why I've been advocating for the uber-patch feature. My experience with submitting patches (several different projects) has been (a) each patch must be limited to one fix or enhancement, and (b) should not result in merge conflicts when the dev applying the patch applies the patch.
I've been running an open source project for a decade now, so I can tell you from experience that a lot of patches come in that do multiple things. You can often tell that they were built up in stages, each an independent step worth a separate checkin, but because they didn't have checkin privileges, they had to submit the whole mess as a single big patch.
I will predict that if Fossil ever *does* get an uber-patch feature, that I'll still get intermingled hairball patches. Still, at least it will give the outsiders a *chance* to do the right thing.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
