Harshavardhana 434e5c0cfe allow preserving legacyXLv1 with inline data format (#11951) ... current master breaks this important requirement we need to preserve legacyXLv1 format, this is simply ignored and overwritten causing a myriad of issues by leaving stale files on the namespace etc. for now lets still use the two-phase approach of writing to `tmp` and then renaming the content to the actual namespace.		2021-04-01 22:12:03 -07:00
..
ISSUE_TEMPLATE	fix: the versioning/object lock documentation appropriately (#9988)	2020-07-08 08:44:43 -07:00
workflows	allow preserving legacyXLv1 with inline data format (#11951)	2021-04-01 22:12:03 -07:00
ISSUE_TEMPLATE.md	fix: the versioning/object lock documentation appropriately (#9988)	2020-07-08 08:44:43 -07:00
lock.yml	fix: the versioning/object lock documentation appropriately (#9988)	2020-07-08 08:44:43 -07:00
logo.svg	Migrate config to KV data format (#8392)	2019-10-22 22:59:13 -07:00
PULL_REQUEST_TEMPLATE.md	Add Optimization as a type of change (#11221)	2021-01-05 14:53:52 -08:00
stale.yml	update stale to ignore 'do not close' label	2020-08-30 20:45:03 -07:00