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?
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 On 2019/12/18 12:50:17, Nathan Hartman <hartman.nat...@gmail.com> wrote: > On Wed, Dec 18, 2019 at 5:46 AM David Sidrane <davi...@apache.org> wrote: > > > > 5 issue one pull request from your fork nuttx/apps to apache nuttx/apps > > master branch > > > > Are you suggesting we have one repo NuttX with 2 folders apps and nuttx? > > > > That will simplify everything! - but I suspect we will receive STRONG > > arguments against it. > > > Yes, such as what will those of us do who have our own custom apps? Not > everyone uses e.g. NSH. Some products are more deeply embedded than others. > > i would oppose combining those two repos into one because i agree with the > concept that we should not make the user's life harder for our convenience. > > Most changes only affect only one repository or the other. For the much > smaller number of changes that affect both, we should have some special > handling. > > Nathan >
