sebb wrote:
Sorry, that's not what I meant.
The Avalon CLI code is a *different* implementation of CLI, but which
happened to have the same problem.
To use Avalon instead of another CLI would require quite a few
application code changes.
[And vice-versa, moving from Avalon to another CLI would mean lots of
code changes. This is why the Avalon code was fixed and submitted.]
Ah, right, gotcha.
So the point was that the Commons-CLI devs should be able to find a
solution in the Avalon-CLI code...assuming they are still similar
enough, or have they never had a shared ancestry?
Cheers,
n
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
