The SAIO documentation numbering scheme is crazy

Bug #663421 reported by gholt
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
Fix Released
Undecided
Unassigned

Bug Description

1 2 3 4 5 6 1 1? I tried to determine the algorithm used, but failed. We should either fix the numbering or document the algorithm used.

Related branches

Revision history for this message
Anne Gentle (annegentle) wrote :

I think that we'll have to split the SAIO doc into two sections - one for loopback, one for partitions - to get the numbering right. I can take a stab at that.

Chuck Thier (cthier)
Changed in swift:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.