We need the ability to configure the maximum number of journal entries (i.e. revisions) to be copied by oak-run segment-copy. This way we can void timeout issues when transferring a large journal over the network with the sole purpose to compact the repository.
For this we can add a new optional argument --last <REV_COUNT>, with the same semantics as oak-run check. If the argument is used, but a specific number of revisions is not specified, the tool will copy by default only the last revision.