Lines Matching full:upstream
93 * If the module has an external (upstream) project repository, the module
94 repository should preserve the upstream repository folder structure.
109 Synchronizing with upstream
116 synchronizing a module with upstream it is mandatory to document the
123 with upstream code base, may only be applied via pull requests. These pull
145 **Updating modules with a diff from upstream:**
146 Upstream changes brought as a single *snapshot* commit (manual diff) in a
150 upstream history in the module repository.
155 the external project is not hosted in an upstream Git repository.
157 The commit message is expected to identify the upstream project URL, the
158 version to which the module is updated (upstream version, tag, commit SHA,
161 **Updating modules by merging the upstream branch:**
162 Upstream changes brought in by performing a Git merge of the intended upstream
166 This approach is applicable to modules with an upstream project Git repository.
167 The main advantages of this approach is that the upstream repository history
201 * regularly synchronize the module repository with its upstream
206 soon as the fixes are available in the upstream code base
256 design or functionality should be discouraged, if the module has an upstream
258 upstream project, directly.
289 the corresponding upstream project bugs in Zephyr. These bug reports
386 Certain external projects provide test suites that reside in the upstream
1167 module related files and changes in relation to upstream need to be maintained