What about the people who are just learning Nuttx? Simple is
relative. I can see how a check out of one folder would make it hard
in your setup and simple for the New folks is'nt that way we are here
to grow the project?
users should not need to learn details of the workflow
BTW: your argument is solve by sub modules. You would just check out
from nuttx repo
It is also very helpful to have multiple remotes
nuttx
nuttx ASF nuttx repo
apps
nat nathan's apps repo
nuttx ASF apps repo
git fetch nuttx
git log nuttx/apps - hmm that changed in make in afd890
git reset --hard nat/apps
git cherry-pick afd890
Please no... save the github chatter for another day, another thread.
I refuse to even look at that
Requirements specification is a top-down activity. It is only driven by
end users needs and project objects. NOT by implementation. That is
the nature of System Engineering: top-down
Design for an implementation, on the other hand, is usually a bottoms-up
activity: You implement the lowest level foundations of the system and
build on top of that to complete the full functional requirements.
This is extreme bad, bad engineering to drive system functional
requirements base on pre-determined implementation of the lowest level.
It is a terrible, unprofessional practice. We need to keep proper
top-down system engineering practices, and not get derailed by this low
level stuff.
We do indeed need pick the nicest dress from show room window based upon
what we really want, not be rummaging through the bargain for the
cheapest thing.
Let's get profressional!
Greg
