-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said:
>> It's another indicator to me that the mokopatch methodology by >> disallowing it to persist in SCM actively pushes us backwards. > > But it does persist ! Look at the commitlog entry. It's all there. The structure doesn't persist in our output for upstream: unless I misunderstood your whole point there about dismembering the patches. Also if we take the hit of arranging things for upstream per-incoming-patch, as the number of incoming patches increases the maintainer suffering level increases linearly. Whereas if we did it prior to a push upstream, assuming that we were able to form a methodology that would work, it would be much less sensitive to how many ingredients went into the pudding, meaning we can scale. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHoyh+OjLpvpq7dMoRAt7AAJwP1Kro3eFytwTQjnf359TG4VfBuwCfYeid Y3dfjQPY0lZgDnRywajdtmQ= =4Gsw -----END PGP SIGNATURE-----
