[PATCH 1/3] bitbake-user-manual/bitbake-user-manual: remove YP as build system

[PATCH 1/3] bitbake-user-manual/bitbake-user-manual: remove YP as build system

[leonardo.sandoval.gonzalez]

From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>

YP is not a build system, so it can not be used as build system example.

Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
---
 doc/bitbake-user-manual/bitbake-user-manual-intro.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/bitbake-user-manual/bitbake-user-manual-intro.xml b/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
index ca7f7246..08d9afdf 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
+++ b/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
@@ -440,7 +440,7 @@
                     Build Checkout:</emphasis>
                     A final possibility for getting a copy of BitBake is that it
                     already comes with your checkout of a larger Bitbake-based build
-                    system, such as Poky or Yocto Project.
+                    system, such as Poky.
                     Rather than manually checking out individual layers and
                     gluing them together yourself, you can check
                     out an entire build system.
-- 
2.12.3

[PATCH 2/3] bitbake-user-manual-metadata: include a space on a append example

[leonardo.sandoval.gonzalez]

From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>

By definition, the override operator "_append" does not include a space,
so include it.

Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
---
 doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
index b37da10a..0cfa53d0 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
+++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
@@ -669,7 +669,7 @@
                         <literallayout class='monospaced'>
      DEPENDS = "glibc ncurses"
      OVERRIDES = "machine:local"
-     DEPENDS_append_machine = "libmad"
+     DEPENDS_append_machine = " libmad"
                         </literallayout>
                         In this example, <filename>DEPENDS</filename> becomes
                         "glibc ncurses libmad".
-- 
2.12.3

[PATCH 3/3] README: new readme file including main aspects of the project

[leonardo.sandoval.gonzalez]

From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>

Includes brief description of the project, pointers to website, documentation,
mailing list and source code.

Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
---
 README | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 README

diff --git a/README b/README
new file mode 100644
index 00000000..95ad4dd3
--- /dev/null
+++ b/README
@@ -0,0 +1,31 @@
+Bitbake
+=======
+
+BitBake is a generic task execution engine that allows shell and Python tasks to be run
+efficiently and in parallel while working within complex inter-task dependency constraints.
+One of BitBake's main users, OpenEmbedded, takes this core and builds embedded Linux software
+stacks using a task-oriented approach.
+
+For information about Bitbake, see the OpenEmbedded website:
+    http://www.openembedded.org/
+
+Bitbake plain documentation can be found under the doc directory or its integrated
+html version at the Yocto Project website:
+    http://yoctoproject.org/documentation
+
+Contributing
+------------
+
+Please refer to
+http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
+for guidelines on how to submit patches, just note that the latter documentation is intended
+for OpenEmbedded (and its core) not bitbake patches (bitbake-devel@lists.openembedded.org)
+but in general main guidelines apply.
+
+Mailing list:
+
+    http://lists.openembedded.org/mailman/listinfo/bitbake-devel
+
+Source code:
+
+    http://git.openembedded.org/bitbake/
-- 
2.12.3

Re: [PATCH 3/3] README: new readme file including main aspects of the project

[akuster]

On 10/02/2017 08:38 AM, leonardo.sandoval.gonzalez@linux.intel.com wrote:
> From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
>
> Includes brief description of the project, pointers to website, documentation,
> mailing list and source code.
>
> Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
> ---
>  README | 31 +++++++++++++++++++++++++++++++
>  1 file changed, 31 insertions(+)
>  create mode 100644 README
>
> diff --git a/README b/README
> new file mode 100644
> index 00000000..95ad4dd3
> --- /dev/null
> +++ b/README
> @@ -0,0 +1,31 @@
> +Bitbake
> +=======
> +
> +BitBake is a generic task execution engine that allows shell and Python tasks to be run
> +efficiently and in parallel while working within complex inter-task dependency constraints.
> +One of BitBake's main users, OpenEmbedded, takes this core and builds embedded Linux software
> +stacks using a task-oriented approach.
> +
> +For information about Bitbake, see the OpenEmbedded website:
> +    http://www.openembedded.org/
> +
> +Bitbake plain documentation can be found under the doc directory or its integrated
> +html version at the Yocto Project website:
> +    http://yoctoproject.org/documentation
> +
> +Contributing
> +------------
> +
> +Please refer to
> +http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
> +for guidelines on how to submit patches, just note that the latter documentation is intended
> +for OpenEmbedded (and its core) not bitbake patches (bitbake-devel@lists.openembedded.org)
> +but in general main guidelines apply.

Is there any value in providing a sample command:

git send-patch -M -1 --subject-prefix=Bitbake][PATCH --to
bitbake-devel@lists.openembedded.org

- Armin
- armin
> +
> +Mailing list:
> +
> +    http://lists.openembedded.org/mailman/listinfo/bitbake-devel
> +
> +Source code:
> +
> +    http://git.openembedded.org/bitbake/

Re: [PATCH 3/3] README: new readme file including main aspects of the project

[Alexander Kanavin]

On 10/02/2017 07:02 PM, akuster wrote:
> 

> Is there any value in providing a sample command:
> 
> git send-patch -M -1 --subject-prefix=Bitbake][PATCH --to
> bitbake-devel@lists.openembedded.org

ak@kanavin-desktop:~/development/poky/meta$ git send-patch
git: 'send-patch' is not a git command. See 'git --help'.


Should be 'git send-email'.

Alex

Re: [PATCH 3/3] README: new readme file including main aspects of the project

[akuster]

On 10/02/2017 09:06 AM, Alexander Kanavin wrote:
> On 10/02/2017 07:02 PM, akuster wrote:
>>
>
>> Is there any value in providing a sample command:
>>
>> git send-patch -M -1 --subject-prefix=Bitbake][PATCH --to
>> bitbake-devel@lists.openembedded.org
>
> ak@kanavin-desktop:~/development/poky/meta$ git send-patch
> git: 'send-patch' is not a git command. See 'git --help'.
>
>
> Should be 'git send-email'.

correct.

>
> Alex

Re: [PATCH 3/3] README: new readme file including main aspects of the project

[Leonardo Sandoval]

 
> Is there any value in providing a sample command:
> 
> git send-patch -M -1 --subject-prefix=Bitbake][PATCH --to
> bitbake-devel@lists.openembedded.org

yes, I think it adds value, specially for new contributors (also this is an effort to reduce patches that get as attachments to the ML).

> 
> - Armin
> - armin
> > +
> > +Mailing list:
> > +
> > +    http://lists.openembedded.org/mailman/listinfo/bitbake-devel
> > +
> > +Source code:
> > +
> > +    http://git.openembedded.org/bitbake/
> 


-- 
Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>