This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients berker.peksag, brett.cannon, ezio.melotti, josh.r, koobs, martin.panter, ncoghlan, ned.deily, python-dev, vlee, vstinner, willingc, yan12125, zach.ware
Date 2017-05-03.07:42:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1493797334.88.0.602980413267.issue23404@psf.upfronthosting.co.za>
In-reply-to
Content
Could we use "regen-*" as the pattern for the file regeneration targets?

I'd expect "make rebuild-all" to be akin to "make clean && make", since in the context of a C project, "build" maps to "generate the output binaries" for me.
History
Date User Action Args
2017-05-03 07:42:14ncoghlansetrecipients: + ncoghlan, brett.cannon, vstinner, ned.deily, ezio.melotti, python-dev, berker.peksag, martin.panter, zach.ware, koobs, willingc, josh.r, vlee, yan12125
2017-05-03 07:42:14ncoghlansetmessageid: <1493797334.88.0.602980413267.issue23404@psf.upfronthosting.co.za>
2017-05-03 07:42:14ncoghlanlinkissue23404 messages
2017-05-03 07:42:14ncoghlancreate