On Sun, May 11, 2014 at 11:55:01PM -0700, Jarno Rajahalme wrote:
> Array splicing was broken when multiple elements were being moved,
> resulting in the priority order being mixed. This came up when the
> highest priority rule from a subtable was removed and the subtable
> needed to be moved down
On May 12, 2014, at 8:48 AM, Ben Pfaff wrote:
> On Mon, May 12, 2014 at 08:43:10AM -0700, Jarno Rajahalme wrote:
>>
>> On May 12, 2014, at 8:36 AM, Ben Pfaff wrote:
>>
>>> On Sun, May 11, 2014 at 11:55:01PM -0700, Jarno Rajahalme wrote:
Array splicing was broken when multiple elements we
On Mon, May 12, 2014 at 08:43:10AM -0700, Jarno Rajahalme wrote:
>
> On May 12, 2014, at 8:36 AM, Ben Pfaff wrote:
>
> > On Sun, May 11, 2014 at 11:55:01PM -0700, Jarno Rajahalme wrote:
> >> Array splicing was broken when multiple elements were being moved,
> >> resulting in the priority order b
On May 12, 2014, at 8:36 AM, Ben Pfaff wrote:
> On Sun, May 11, 2014 at 11:55:01PM -0700, Jarno Rajahalme wrote:
>> Array splicing was broken when multiple elements were being moved,
>> resulting in the priority order being mixed. This came up when the
>> highest priority rule from a subtable w
On Sun, May 11, 2014 at 11:55:01PM -0700, Jarno Rajahalme wrote:
> Array splicing was broken when multiple elements were being moved,
> resulting in the priority order being mixed. This came up when the
> highest priority rule from a subtable was removed and the subtable
> needed to be moved down
Array splicing was broken when multiple elements were being moved,
resulting in the priority order being mixed. This came up when the
highest priority rule from a subtable was removed and the subtable
needed to be moved down the priority list by more than one position.
Signed-off-by: Jarno Rajaha
