> The recent change which added a fatal for not having a default or > user set value for a parameter broke X86_FS. There wasn't any way to > really know that was going to happen since it wouldn't show up until run > time and X86_FS isn't generally in a known condition, so I'm not all > that upset about the actual breakage. The fix is relatively simple, but > unfortunately I didn't realize my recent pull broke things until I'd > moved a considerable number of patches into regular changesets. I could > push as is and fix the problem later in the history, but then all of the > steps between the param change and now will be broken. I think there's a > way to turn changesets back into patches which I'll try. Is there a > better way to handle this? Also, is it really correct for all parameters > to have to have a default value or a user set value? What about things > that are optional? It's not possible to set a default value of "None" as > far as I know.
A combination of hg export and hg strip will help turn your changesets back into patches. As Ali says. Backup before you do this. I actually would cp -a the directory, not clone just to make sure you have everything. Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
