include repo command lines and basic explanation of master-next along with caveats.
Signed-off-by: Christian Betz <[email protected]> --- README | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/README b/README index af19e1f..6edc544 100644 --- a/README +++ b/README @@ -47,3 +47,23 @@ git format-patch -s --subject-prefix='fsl-community-bsp-platform][PATCH' origin When sending patches, please use something like: git send-email --to [email protected] <generated patch> + +Using Development and Testing Branches +-------------------------------------- + +Replace the 'repo init' command above with one of the following: + +master: for developers + +$: repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b master + +master-next: for intrepid developers and testers + +Patches are typically merged into master-next and then are merged into +master after a testing and comment period. It's possible that master-next +has something you want or need. But it's also possible that using +master-next will break something that was working before. Use with caution. + +$: repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b master-next + + -- 1.7.9.5 _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
