Mailing List Archive

Quoting interchange-cvs@developer.akopia.com (interchange-cvs@developer.akopia.com):
> CVS activity by user 'bob':
> interchange/dist/lib/UI/pages/admin access_permissions.html,1.7.6.11,1.7.6.12
> Update of /var/cvs/interchange/dist/lib/UI/pages/admin
> In directory interchange.redhat.com:/tmp/cvs-serv22741
>
> Modified Files:
> Tag: DEV_4_7_0
> access_permissions.html
> Log Message:
> swapped column headings to agree with table cells in Edit Permissions section
>

Hmm. I had fixed this just a bit ago by swapping the array elements and
not the headings -- we are now out of sync again! 8-)

I changed it back.

You might want to check the CVS update when you do this type of
thing in the future....

--
Red Hat, Inc., 3005 Nichols Rd., Hamilton, OH 45013
phone +1.513.523.7621 <mheins@redhat.com>

Fast, reliable, cheap. Pick two and we'll talk. -- unknown

On Mon, 9 Jul 2001, Mike Heins wrote:

> > Modified Files:
> > Tag: DEV_4_7_0
> > access_permissions.html
> > Log Message:
> > swapped column headings to agree with table cells in Edit Permissions section
>
> Hmm. I had fixed this just a bit ago by swapping the array elements and
> not the headings -- we are now out of sync again! 8-)
>
> I changed it back.
>
> You might want to check the CVS update when you do this type of
> thing in the future....

This was my fault. I glanced at the update you made, saw @some and @more
being used as keys for a hash slice, thought the order problem still
wasn't fixed yet, and stupidly forgot to look below where the "for (@all)"
kicks in. Bob and I swapped the column header text on his machine and it
seemed so unscrewupably simple that I said to commit it without testing.

Moral of the story: always test before you commit.

Did I mention ALWAYS? :)

Jon