Miloslav Trmač 4dab4d97de RFC: Rename Image.PushImage to Image.PushImageToHeuristicDestination ...

The goal is to be very explicit about which functions try to heuristically
guess what is the expected format of the string.  Not quite "shaming"
the users, but making sure they stand out.

RFC:
- Is this at all acceptable? Desirable?
- varlink ExportImage says "destination must have transport type";
  should it be using alltransports.ParseImageReference
  + PushImageToReference, then?

(While touching the call in cmd/podman, also remove a commented-out
older version of the call.)

Should not change behavior (but does not add unit tests).

Signed-off-by: Miloslav Trmač <mitr@redhat.com>

Closes: #1176
Approved by: rhatdan

2018-08-01 18:22:59 +00:00

..

testdata

Split refNamesFromImageReference from Runtime.getPullListFromRef

2018-08-01 18:22:58 +00:00

docker_registry_options.go

save and load should support multi-tag for docker-archive

2018-05-25 15:15:47 +00:00

filters.go

Spell check strings and comments

2018-05-25 08:45:15 +00:00

image_test.go

Skip unit tests which require storage when not running as root

2018-07-26 20:47:31 +00:00

image.go

RFC: Rename Image.PushImage to Image.PushImageToHeuristicDestination

2018-08-01 18:22:59 +00:00

parts_test.go

Add unit tests for imageParts

2018-07-23 12:44:38 +00:00

parts.go

Use the result of reference.Parse when checking for digests.

2018-07-23 12:44:38 +00:00

pull_test.go

Remove the error return value from getPullRefName

2018-08-01 18:22:58 +00:00

pull.go

Remove an unnecessary use of alltransports.ParseImageName

2018-08-01 18:22:59 +00:00

signing_options.go

Stage3 Image Library

2018-03-14 20:21:31 +00:00

utils.go

Inline getTags into its only user

2018-07-23 12:44:38 +00:00