interrupting rev-upgrade with v2.3.5 or a post-v2.3.5 master

[René J.V. Bertin]

Hi,

I understand that the latest update introduced better handling of interrupts. Is it now safe to interrupt the rev-upgrade process done after a `port upgrade` (knowing that I configured it to check only)?

I often miss an option to skip that step (esp. the first of the day which always takes longer) but I suppose that being able to interrupt it safely will work just as fine.

Thanks,
R.