Message83239
This is specific to the Python tracker, which Rietveld tries to avoid.
You could maintain this as a locally modified version, but a better
approach would be to make just enough changes to upload.py itself so
that you can write the rest of this script as a *wrapper* around
upload.py. That's how the Chrome people manage their workflow, and
that's a generally recommended approach: the wrapper does the
project-specific stuff, passing everything to upload.py for the actual
interaction with Rietveld.
PS. What do you mean by "wish we could expunge the deleted ones"? If
you delete a Rietveld issue it is really gone. If you merely close it,
you can still delete it later. But I'm probably missing something.
http://codereview.appspot.com/25073 |
|
Date |
User |
Action |
Args |
2009-03-06 05:36:30 | gvanrossum | set | recipients:
+ gvanrossum |
2009-03-06 05:36:28 | gvanrossum | link | issue400608 messages |
2009-03-06 05:36:26 | gvanrossum | create | |
|