Miloslav Trmač 449116af19 Remove imageParts.{isTagged,registry,name,tag} ... Finally, these members no longer have any users. Future users should usually call referenceWithRegistry / normalizedReference, and work with the returned value, instead of reintroducing these variables. Similarly, direct uses of unnormalizedRef should be rare (only for cases where the registry and/or path truly does not matter). Should not change behavior. Signed-off-by: Miloslav Trmač <mitr@redhat.com>		2019-01-14 04:07:24 +01:00
..
testdata	Split refNamesFromImageReference from Runtime.getPullListFromRef	2018-08-01 18:22:58 +00:00
docker_registry_options.go	Minimally update for the DockerInsecureSkipTLSVerify type change	2018-12-06 23:34:59 +01:00
errors.go	add podman container|image exists	2018-11-26 09:19:39 -06:00
image.go	FIXME? Introduce imageParts.suspiciousRefNameTagValuesForSearch	2019-01-14 04:07:24 +01:00
image_test.go	Return a reference.Named from normalizedTag	2019-01-14 04:07:23 +01:00
parts.go	Remove imageParts.{isTagged,registry,name,tag}	2019-01-14 04:07:24 +01:00
parts_test.go	Remove imageParts.{isTagged,registry,name,tag}	2019-01-14 04:07:24 +01:00
prune.go	Add ability to prune containers and images	2018-12-05 19:57:54 -06:00
pull.go	Use getPullRefPair / getSinglePullRefPairGoal in pullGoalFromPossiblyUnqualifiedName	2019-01-14 04:07:23 +01:00
pull_test.go	Use imageParts.referenceWithRegistry in pullGoalFromPossiblyUnqualifiedName	2019-01-14 04:07:23 +01:00
signing_options.go	Stage3 Image Library	2018-03-14 20:21:31 +00:00
utils.go	FIXME? Introduce imageParts.suspiciousRefNameTagValuesForSearch	2019-01-14 04:07:24 +01:00