stopping/aborting obsolete jenkins jobs

Hi, It happened to me quite a lot lately, that I pushed a new patchset for a change, before jenkins finished running relevant jobs for previous patchsets, in some cases even before it started running some of them. Perhaps in such a case we should stop (if running) or disable/abort (if not yet running) all the jobs except for the ones running for the latest patchset? This will both give quicker results for the dev/maint and lower the load on the slaves. Best, -- Didi