On Wed, Dec 25, 2019 at 6:45 PM Justin Mclean <jus...@classsoftware.com> wrote:
> > People on this list have indicated that they use NuttX released with > Apache SVN. > > The releases are placed in a ASF SVN system to be distributed by the > mirror system yes. I think Greg means that users are getting the release tarballs and checking the code into their own version control system, which may be Subversion, Git, proprietary SCM software, etc., or possibly no version control at all (think "installing" NuttX to disk like a library). Therefore the release must be SCM-agnostic. (This is why it was a bug when a recent change to the build system assumed that git was available. I detected that because I keep NuttX in Subversion.) For this discussion, it's irrelevant that ASF puts release tarballs in Subversion. Users who download the tarballs need not know or care because from their perspective it's like any other download. Subversion is just the back end storage for this. As far as contributors, some may use Git, create a Git clone, and then generate either a patch or a PR. But we do *not* want to require using Git. What's not clear to me is how do contributors who *don't* use Git send changes to us? Do they use plain 'diff'? Do they use their SCM to generate git-compatible patches? Do they zip up their entire tree? Also I'd like to emphasize that ANYONE can contribute whether they can commit to the NuttX repository or not. What we need to do is document what steps to take, in the Confluence document that we are working on right now. And we want everyone who is interested to participate so that our workflow will be a product of the whole community. You'll find it much easier to adopt the workflow if you helped create it!!! Thanks, Nathan
