Should I be able to see patches submitted to the meta-freescale@yoctoproject.org in the meta-freescale Archives or in my inbox once they are published to the list?
Do patches go through some kind of review before they are posted to the wider distribution list? I tried to send a patch for some of user guide documentation last week but have not seen anything of it yet. I did notice that by copy and pasting my way through the documentation instructions I ended up with [<Documentation] in my subject, which looked a bit odd. I tried to submit the patch again on the 31st with an adjusted subject that started [Documentation] but I have not seen anything of that either. My non-patch message made it out within 3 hours. Thomas Thorne Software Engineer Net2Edge Limited On 24/08/16 17:56, Thomas Thorne wrote: > Replace 'Jethro' with 'Krogoth' and '2.0' with '2.1' > > Signed-off-by: Thomas Thorne <thomas.tho...@net2edge.com> > --- > FAQ/source/conf.py | 6 +++--- > release-notes/source/conf.py | 2 +- > user-guide/source/conf.py | 6 +++--- > user-guide/source/nsteps.rst | 2 +- > 4 files changed, 8 insertions(+), 8 deletions(-) > > diff --git a/FAQ/source/conf.py b/FAQ/source/conf.py > index a2792a6..00eaebd 100644 > --- a/FAQ/source/conf.py > +++ b/FAQ/source/conf.py > @@ -47,10 +47,10 @@ copyright = u'2014, Freescale Community BSP Team' > # |version| and |release|, also used in various other places throughout the > # built documents. > # > -# The short X.Y version. > -version = '1.5' > +# The short X.Y version or version name if applicable. > +version = 'krogoth' > # The full version, including alpha/beta/rc tags. > -release = '1.5' > +release = '2.1' > > # The language for content autogenerated by Sphinx. Refer to documentation > # for a list of supported languages. > diff --git a/release-notes/source/conf.py b/release-notes/source/conf.py > index 6115217..0ea97f1 100644 > --- a/release-notes/source/conf.py > +++ b/release-notes/source/conf.py > @@ -50,7 +50,7 @@ copyright = u'2013-2016, FSL Community BSP Team' > # |version| and |release|, also used in various other places throughout the > # built documents. > # > -# The short X.Y version. > +# The short X.Y version or version name if applicable. > version = 'krogoth' > # The full version, including alpha/beta/rc tags. > release = '2.1' > diff --git a/user-guide/source/conf.py b/user-guide/source/conf.py > index 558f919..7c9f536 100644 > --- a/user-guide/source/conf.py > +++ b/user-guide/source/conf.py > @@ -47,10 +47,10 @@ copyright = u'2014, Freescale Community BSP Team' > # |version| and |release|, also used in various other places throughout the > # built documents. > # > -# The short X.Y version. > -version = '1.6' > +# The short X.Y version or version name if applicable. > +version = 'krogoth' > # The full version, including alpha/beta/rc tags. > -release = '1.6' > +release = '2.1' > > # The language for content autogenerated by Sphinx. Refer to documentation > # for a list of supported languages. > diff --git a/user-guide/source/nsteps.rst b/user-guide/source/nsteps.rst > index df1c107..a64cca7 100644 > --- a/user-guide/source/nsteps.rst > +++ b/user-guide/source/nsteps.rst > @@ -16,7 +16,7 @@ Build and boot in *N*-steps > $ cd fsl-community-bsp > fsl-community-bsp $ repo init \ > -u > https://github.com/Freescale/fsl-community-bsp-platform \ > - -b jethro > + -b krogoth > fsl-community-bsp $ repo sync > > 4. Select your machine (:ref:`machines`) and prepare the environment for > bitbake::
signature.asc
Description: OpenPGP digital signature
-- _______________________________________________ meta-freescale mailing list meta-freescale@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-freescale