Aaron Lehmann cfb0b7aa77 Fix uses of "int" where "int64" should be used instead ... Some structures use int for sizes and UNIX timestamps. On some platforms, int is 32 bits, so this can lead to the year 2038 issues and overflows when dealing with large containers or layers. Consistently use int64 to store sizes and UNIX timestamps in api/types/types.go. Update related to code accordingly (i.e. strconv.FormatInt instead of strconv.Itoa). Use int64 in progressreader package to avoid integer overflow when dealing with large quantities. Update related code accordingly. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>		2015-07-31 16:31:40 -07:00
docs	Fix uses of "int" where "int64" should be used instead	2015-07-31 16:31:40 -07:00