There are a few outliers with unhelpful references to UMICH-1136, https://sakaiproject.atlassian.net/browse/UMICH-1167#icft=UMICH-1167 (e.g. gradebook, signup), but this looks good enough for the time spent on this. If we upgrade to Sakai 10, we'll just have to spend a little more time double-checking the svn logs for the actual SAK JIRAs.

Below is the committed revision#, I couldn't commit all in one as i had some error popping up.
presence/rwiki/samigo- Committed revision 320116.
signup/- Committed revision 87713.
assignment/user - Committed revision 320117.
announcement/shortenedurl- Committed revision 320118.
calendar/lessonbuilder/site-manage -Committed revision 320119.
msgcntr/polls/ sitestats/syllabus/web/ -Committed revision 320120.
content/gradebook/jobscheduler/podcasts/search/sections - Committed revision 320121.

If CTools needs to upgrade to Sakai 10, we need a way to audit the patches applied to Sakai 2.9, so we can determine which SAK JIRAs need to be applied to Sakai 10 and which SAK JIRAs are already included in the Sakai 10 release. This is the purpose of the patches.txt file.

Referencing https://sakaiproject.atlassian.net/browse/UMICH-1167#icft=UMICH-1167 in the patches.txt file does not help with this audit. The patches.txt file should be updated with SAK JIRAs that were applied.

Additionally, you need to provide a way for someone to verify the changes to the patches.txt file (e.g. svn commit revision would help).