The branches are expressed as a hyphen-delimited series of change set ids, for example, 12-7-2-0. The first entry is assumed to be the top-most-deployed entry - the others are assumed to be linked via baseline contiguously, but can be specified in any order. The reason for the special meaning inherent in the first entry is that we need to be able to set a sensible value for the 'active change set' in order to prime the various views we need to access - they all depend on a correct current definition of the special 'active_change_sets' view.]]> The branches are expressed as a hyphen-delimited series of change set ids, for example, 12-7-2-0. The first entry is assumed to be the top-most-deployed entry - the others are assumed to be linked via baseline contiguously, but can be specified in any order. The reason for the special meaning inherent in the first entry is that we need to be able to set a sensible value for the 'active change set' in order to prime the various views we need to access - they all depend on a correct current definition of the special 'active_change_sets' view.]]> Note: PrefixTree is an object but treated separately.]]> Note: PrefixTree is an object but treated separately.]]> Note: we originally wrote this more simply with a difference object in the DELETE payload, but it turns out that DELETE operations should not carry payload, so we must obtain our information purely from the URI. (A consequence is that we need the PMD override for UseObjectForClearerAPI).

]]> Note: we originally wrote this more simply with a difference object in the DELETE payload, but it turns out that DELETE operations should not carry payload, so we must obtain our information purely from the URI. (A consequence is that we need the PMD override for UseObjectForClearerAPI).

]]>