For most recipes, deploying output files to the target is straightforward - the files go into the root filesystem, but for the kernel it's not that easy. It's device-specific in a lot of cases. If we want people to be able to test their kernel changes though we should provide at least basic support. The following will need to be handled: 1) Kernel image itself 2) Modules 3) Update to any bootloader configuration if necessary If the tool doesn't have enough information to determine what to do, then it should error out.
Bulk move from 4.99 or 0.00 to 5.99
bulk change to add Saul's non-WR address.
Bulk change: Remove Saul's old WR address.