> a t2 tree only has one set of current versions, so this kind of per version > patches is not generally needed. When the package is updated and the patch > no longer applies, *it is just discarded* - >
I feel that it is a waste of valuable work for always up-keeping with latest package versions and discarding older ones. > otherwise the tree would also grow to an even more exhausting clutter to > maintain, navigate, and exchange. > IMHO, I doubt that it would be that intricate since these are per package configs and patches; they're not binaries. In addition, if we defined policies where version patches should go, they should not be hard to maintain/navigate/exchange. -toan
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
