Liam Beguin <liambeg...@gmail.com> writes: > Sorry for the delay, I don't mind switching to C but it would probably > be easier to see if the scripted version gets approved first. > If it does, I could then get started on the C implementation. > If you prefer I could also forget about the scripted version, make a C > implementation work and see if that gets approved.
I am not sure what "approved" would mean in the context of this project, though ;-) Your patch to the scripted version would certainly not be in the upcoming release. If you define the "approval" as "it is queued to my tree somewhere", the patch would start its life like everybody else by getting merged to the 'pu' branch, where there already is a topic that removes the code you patch your enhancement into. The list _can_ agree that it is a good idea to have an option to populate the todo list with shortened insn words from the beginning (instead of merely accepting a short-hand while executing), which is what your patch wants to do, without actually having the updated scripted "rebase -i" merged in any of the integration branches in my tree. If you meant by "approval" to have such a list concensus, I think you may already have one. I personally do not think it is a great idea but I do not think it is a horrible one, either. As long as it is an opt-in feature that many people find useful (which may be the case already, judging from the list traffic), I do not mind ;-)
