Comment 1 for bug 131858

Well, the new setting is more logical, since adding "savedefault" only makes sense if the user has specified "default saved" in menu.lst, in which case the user is already sophisticated and can turn on the savedefault option as well.

The old setting would leave many set-ups broken (see bug references in the changelog). There could be a possibility to have update-grub (or .postinst?) check for "saved" and then guess that the user wants to enable savedefault, but I am not sure if it's worth the added complexity.