Yes it can, and it can be un-needlesly complicated if not done right -
and so that's why I floated the question, as it seems that it is
implicit in the design of the way that newt produces a software part
that it should be traceable. I would think, it needs the specific git
commands - the "magic recipe" to be documented in a tutorial.
Personally I'm not going to write any software outside of a sandbox, as
if/when things go wrong - which they do in embedded software very easily
- a git environment makes recovery relatively easy .
Neil
On 2/1/2017 10:27 AM, Alan Graves wrote:
I certainly struggle to understand git all the time and I'm likely to be wrong
here, but can't a git repository have sub-projects within the larger
super-project?
ALan
-----Original Message-----
From: Neilh [mailto:[email protected]]
Sent: Wednesday, February 01, 2017 9:36 AM
To: [email protected]
Subject: git for all next directories
Hi
Just got a dumb question to ask - I'm working through the tutorials and its
well explained the standard SCM/git is on
"myproj/repos/apache-mynewt-core ((mynewt_1_0_0_b1_tag))]$"
However, after the basic tutorial, with a working "newt" environment, I need to have the whole sandbox
from "myproj" be under SCM. Then with all those text files, if something stops working I can trace back.
Also, it seems like as a project matures I could have apps be a separate repository - this is starting to look
quite complex - and would also need to be integrated into creating a signed image "newt create-image
<app> 1.0.0" .
https://mynewt.apache.org/latest/newt/command_list/newt_create_image/
Seems the simplest scenario to begin with is setting up a top level git from
"myproj", and at least have the capability to snapshot it from there.
Are there any thoughts/linkages/tutorial on doing this?
--
Neil Hancock
