bazel - a fast, scalable, multi-language and extensible build system

	Commit message (Collapse)	Author	Age
*	Have DigestMap support multiple hash functions.	tomlu	2018-08-15
\| \| \| \| \|	RELNOTES: None PiperOrigin-RevId: 208837641
*	Add easy access to MessageDigests in DigestHashFunction	ccalvarin	2018-08-13
\| \| \| \| \| \| \|	Move the message-digest cloning to DigestHashFunction and out of Fingerprint, to make it possible to configure Fingerprint to use different hash functions. We keep the default MD5 for now, we'd like it to use the global default but want to isolate the configuration change from any change adding potential contention. RELNOTES: None. PiperOrigin-RevId: 208502993
*	Add a normal startup-option for setting the digest function.	ccalvarin	2018-08-01
\| \| \| \| \| \| \| \| \|	We continue to support the jvm property -Dbazel.DigestFunction, for backwards compatibility, but this will go away. The startup-option is marked experimental for now as we iron out issues. (note: leaving this out of release notes until the experimental tag is removed) As part of this refactor, the default constructor calls for FileSystem and derived classes will now use this default. This should remove the need for constructors that accept custom hash functions. RELNOTES: None. PiperOrigin-RevId: 207035217
*	Move HashFunction out of FileSystem, and turn it into a class, instead of an ↵	ccalvarin	2018-06-21
	enum. Now that we aren't using enum names for the hash functions, we also accept the standard names, such as SHA-256. RELNOTES: None. PiperOrigin-RevId: 201624286