Mark> Is it acceptable to commit a change (to the trunk or py3k, not to
Mark> the release branches) solely for the purpose of getting more
Mark> information about a failure?
I think it would be kind of nice if you could force a buildbot to use a
specific branch. You could then check your diagnostic changes in on a
branch meant just for that purpose. Once you're done with your changes you
could simply delete the branch.
Skip
_______________________________________________
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
