[linuxsh-dev] [RFC] LinuxSH code reorg

[NIIBE Y. <gn...@m1...>]

Thanks a lot.  Well written.  I think that change of structure and the
move towards only maintaining SuperH portion are good idea.  If
possible, it's good we can adopt such a new way of development for
2.5.

I'd like to add some.

(1) "Patch Manager"
We have "Patch Manager", but it's almost non-functional (no one care
it).  I think that the future direction is remove using "Patch
Manager" and require people to send all the changes to review.

(2) Changes done in mainline
Occasionally, the changes will be done in the mainline source.
We need to include the changes to our repository.  This'd be a kind
of special work.  Does it require to send the changes to review?
Who will do it, and how?  Sometimes we can't identify who does the
change and don't understand the intention why we need the change.

(3) Testing
It would be good if we can maintain some sort of success/failure table
with version and/or date.  It is good for tracking bug introduced.
Performance test is also good.
--