Alexander Vollschwitz

@danielkza Thanks for this great PR! And sorry it took me so long to react! Unfortunately, dregsy is just a private side project, and I don't get as much time...

>> a test case for the Docker relay is missing > is the choice of relay relevant for this functionality? I guessed it was not, but I can of course...

I think there are two 'levels' of insecure here. The meaning of `skip-tls-verify: true` is quite literally to skip TLS verification of the server, but not to drop to HTTP....

Thanks for your interest & for extending dregsy! So far I've only skimmed the changes in your fork, so these are just a few initial, high level thoughts & comments:...

Regarding the approach with your current fork, that's no problem at all, I understand your situation. It's important that you get the problem at hand solved quickly. If dregsy could...

Running tasks in parallel can be advantageous when the system running *dregsy* has a significantly faster network connection than any of the involved source and/or target registries. In the opposite...

Great PR! Thanks! A dry-run is definitely a good idea. Before going into review, could you please remove the commit for building on AMR64? This is a separate concern and...

I've just merged another PR, so you will have to rebase. Sorry about that! But there are not that many conflicts, so it shouldn't be too complicated. Mea culpa

I did a first review. Here are my comments: - I think we should push dry run handling into the relays. The code for expanding source tag lists is already...

I've just noticed that starting with *Skopeo* 1.8.0, the `sync` command which we use in *dregsy* also introduces a dry-run mode. I think we should take advantage of that once...