> Trying to expand our buildbot infrastructure to accept patches to test > out or some patch queue manager might be nice, but I want to be > realistic with what we have now. That's why I am not worrying about > this email feature; until I know that we will actually use it and have > the manpower to implement it I consider it a perk that might never be > used. It's all great to dream about the future and what could be, but > that is far beyond just trying to get us to switch to a DVCS and is > just icing on the cake.
It's not an email feature. It's about bundling revisions in a way that may be cheaply sent or attached in any way wanted. It is useful in practice. Attachments to bugs, mails, and so on are not novelty nor optimization. Check out how many patches you have attached to the bug tracker. Now consider how better would it be if these patches carried history information which allowed them to be merged considering context, and carried logs, authorship information, and incremental history. -- Gustavo Niemeyer http://niemeyer.net _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
