Aaron Lehmann 34a611be4f Make v1 pull/push output consistent with v2 ...

- Use layer DiffIDs for progress output in v1 push. This makes the
  output consistent with v2 pushes, which means that a fallback to v1
  won't start progress bars for a different set of IDs.

- Change wording used in v1 status updates to be consistent with v2.

Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>
Upstream-commit: 891bbc17ec2623897e32a3b9116cb2047ba70fdd
Component: engine

2015-12-16 15:02:24 -08:00

..

fixtures/validate_manifest

Add distribution package

2015-11-24 09:40:24 -08:00

metadata

Improved push and pull with upload manager and download manager

2015-12-09 19:13:35 -08:00

xfer

Add metadata function to layer store

2015-12-14 16:52:15 -08:00

pull_v1.go

Make v1 pull/push output consistent with v2

2015-12-16 15:02:24 -08:00

pull_v2_test.go

Add own reference package wrapper

2015-12-16 11:58:52 -08:00

pull_v2_unix.go

Add distribution package

2015-11-24 09:40:24 -08:00

pull_v2_windows.go

Add distribution package

2015-11-24 09:40:24 -08:00

pull_v2.go

Do not fall back to the V1 protocol when we know we are talking to a V2 registry

2015-12-16 15:02:03 -08:00

pull.go

Do not fall back to the V1 protocol when we know we are talking to a V2 registry

2015-12-16 15:02:03 -08:00

push_v1.go

Make v1 pull/push output consistent with v2

2015-12-16 15:02:24 -08:00

push_v2_test.go

Improved push and pull with upload manager and download manager

2015-12-09 19:13:35 -08:00

push_v2_unix.go

Add distribution package

2015-11-24 09:40:24 -08:00

push_v2_windows.go

Add distribution package

2015-11-24 09:40:24 -08:00

push_v2.go

Do not fall back to the V1 protocol when we know we are talking to a V2 registry

2015-12-16 15:02:03 -08:00

push.go

Do not fall back to the V1 protocol when we know we are talking to a V2 registry

2015-12-16 15:02:03 -08:00

registry_unit_test.go

Do not fall back to the V1 protocol when we know we are talking to a V2 registry

2015-12-16 15:02:03 -08:00

registry.go

Do not fall back to the V1 protocol when we know we are talking to a V2 registry

2015-12-16 15:02:03 -08:00