Added templates for the README files

author: Thomas Lundström <thomas.lundstrom@enea.com> 2016-04-13 10:00:11 +0200
committer: Thomas Lundström <thomas.lundstrom@enea.com> 2016-04-13 10:00:11 +0200
commit: 2d8585e93fb4885a2e40c5dcac2e4484fa99ad7a (patch)
tree: 6493e8e290b9be07a165a84fd8eade79f999379d
parent: bf70eca95171db379760fec43c072fcd14ecaaa7 (diff)
download: el_manifests-standard-2d8585e93fb4885a2e40c5dcac2e4484fa99ad7a.tar.gz
10 files changed, 180 insertions, 0 deletions
diff --git a/ls1021atwr/.README b/ls1021atwr/.README
new file mode 100644
index 0000000..e3fdf1a
--- /dev/null
+++ b/ls1021atwr/.README
@@ -0,0 +1,9 @@
+This file is a template used to produce the real README. Read that one instead
+________END_OF_HEADER________
+Bla bla bla ...
+________INSERT_BUILD_SEQUENCES_HERE________
+________INSERT_BOOT_SEQUENCES_HERE________
diff --git a/ls1021atwr/README.first b/ls1021atwr/README.first
new file mode 100644
index 0000000..6d08887
--- /dev/null
+++ b/ls1021atwr/README.first
@@ -0,0 +1,27 @@
+This file contains the describing the manifest repo. Not to be confused with the
+file README.
+The manifest repo contains:
+README.first          : This file
+README                : A README file that will be made available for the
+                        customer after repo sync. It contains build and boot
+                        commands and other specific info.
+                        Auto generated using .README and output from ELTF.
+.README               : A template for generating the README file. Currently,
+                        build and boot commands are provided by ELTF and they
+                        are integrated into .README to generate README. This is
+                        quite a mess, but the long term plan is to modify this
+                        in a way that makes the template obsolete.
+manifest_template.xml : A template for default.xml. It contains a list of the
+                        repos together with versions. The versions can be
+                        specified using branches, tags, or hashes.
+default.xml           : This a time-invariant snapshot of manifest_template.xml.
+                        The difference is that all versions are specified as
+                        hashes.
+                        Auto-generated using manifest_template and data from
+                        the remotes.
diff --git a/p2041rdb/.README b/p2041rdb/.README
new file mode 100644
index 0000000..e3fdf1a
--- /dev/null
+++ b/p2041rdb/.README
@@ -0,0 +1,9 @@
+This file is a template used to produce the real README. Read that one instead
+________END_OF_HEADER________
+Bla bla bla ...
+________INSERT_BUILD_SEQUENCES_HERE________
+________INSERT_BOOT_SEQUENCES_HERE________
diff --git a/p2041rdb/README.first b/p2041rdb/README.first
new file mode 100644
index 0000000..6d08887
--- /dev/null
+++ b/p2041rdb/README.first
@@ -0,0 +1,27 @@
+This file contains the describing the manifest repo. Not to be confused with the
+file README.
+The manifest repo contains:
+README.first          : This file
+README                : A README file that will be made available for the
+                        customer after repo sync. It contains build and boot
+                        commands and other specific info.
+                        Auto generated using .README and output from ELTF.
+.README               : A template for generating the README file. Currently,
+                        build and boot commands are provided by ELTF and they
+                        are integrated into .README to generate README. This is
+                        quite a mess, but the long term plan is to modify this
+                        in a way that makes the template obsolete.
+manifest_template.xml : A template for default.xml. It contains a list of the
+                        repos together with versions. The versions can be
+                        specified using branches, tags, or hashes.
+default.xml           : This a time-invariant snapshot of manifest_template.xml.
+                        The difference is that all versions are specified as
+                        hashes.
+                        Auto-generated using manifest_template and data from
+                        the remotes.
diff --git a/qemuarm/.README b/qemuarm/.README
new file mode 100644
index 0000000..e3fdf1a
--- /dev/null
+++ b/qemuarm/.README
@@ -0,0 +1,9 @@
+This file is a template used to produce the real README. Read that one instead
+________END_OF_HEADER________
+Bla bla bla ...
+________INSERT_BUILD_SEQUENCES_HERE________
+________INSERT_BOOT_SEQUENCES_HERE________
diff --git a/qemuarm/README.first b/qemuarm/README.first
new file mode 100644
index 0000000..6d08887
--- /dev/null
+++ b/qemuarm/README.first
@@ -0,0 +1,27 @@
+This file contains the describing the manifest repo. Not to be confused with the
+file README.
+The manifest repo contains:
+README.first          : This file
+README                : A README file that will be made available for the
+                        customer after repo sync. It contains build and boot
+                        commands and other specific info.
+                        Auto generated using .README and output from ELTF.
+.README               : A template for generating the README file. Currently,
+                        build and boot commands are provided by ELTF and they
+                        are integrated into .README to generate README. This is
+                        quite a mess, but the long term plan is to modify this
+                        in a way that makes the template obsolete.
+manifest_template.xml : A template for default.xml. It contains a list of the
+                        repos together with versions. The versions can be
+                        specified using branches, tags, or hashes.
+default.xml           : This a time-invariant snapshot of manifest_template.xml.
+                        The difference is that all versions are specified as
+                        hashes.
+                        Auto-generated using manifest_template and data from
+                        the remotes.
diff --git a/qemuppc/.README b/qemuppc/.README
new file mode 100644
index 0000000..e3fdf1a
--- /dev/null
+++ b/qemuppc/.README
@@ -0,0 +1,9 @@
+This file is a template used to produce the real README. Read that one instead
+________END_OF_HEADER________
+Bla bla bla ...
+________INSERT_BUILD_SEQUENCES_HERE________
+________INSERT_BOOT_SEQUENCES_HERE________
diff --git a/qemuppc/README.first b/qemuppc/README.first
new file mode 100644
index 0000000..6d08887
--- /dev/null
+++ b/qemuppc/README.first
@@ -0,0 +1,27 @@
+This file contains the describing the manifest repo. Not to be confused with the
+file README.
+The manifest repo contains:
+README.first          : This file
+README                : A README file that will be made available for the
+                        customer after repo sync. It contains build and boot
+                        commands and other specific info.
+                        Auto generated using .README and output from ELTF.
+.README               : A template for generating the README file. Currently,
+                        build and boot commands are provided by ELTF and they
+                        are integrated into .README to generate README. This is
+                        quite a mess, but the long term plan is to modify this
+                        in a way that makes the template obsolete.
+manifest_template.xml : A template for default.xml. It contains a list of the
+                        repos together with versions. The versions can be
+                        specified using branches, tags, or hashes.
+default.xml           : This a time-invariant snapshot of manifest_template.xml.
+                        The difference is that all versions are specified as
+                        hashes.
+                        Auto-generated using manifest_template and data from
+                        the remotes.
diff --git a/qemux86/.README b/qemux86/.README
new file mode 100644
index 0000000..e3fdf1a
--- /dev/null
+++ b/qemux86/.README
@@ -0,0 +1,9 @@
+This file is a template used to produce the real README. Read that one instead
+________END_OF_HEADER________
+Bla bla bla ...
+________INSERT_BUILD_SEQUENCES_HERE________
+________INSERT_BOOT_SEQUENCES_HERE________
diff --git a/qemux86/README.first b/qemux86/README.first
new file mode 100644
index 0000000..6d08887
--- /dev/null
+++ b/qemux86/README.first
@@ -0,0 +1,27 @@
+This file contains the describing the manifest repo. Not to be confused with the
+file README.
+The manifest repo contains:
+README.first          : This file
+README                : A README file that will be made available for the
+                        customer after repo sync. It contains build and boot
+                        commands and other specific info.
+                        Auto generated using .README and output from ELTF.
+.README               : A template for generating the README file. Currently,
+                        build and boot commands are provided by ELTF and they
+                        are integrated into .README to generate README. This is
+                        quite a mess, but the long term plan is to modify this
+                        in a way that makes the template obsolete.
+manifest_template.xml : A template for default.xml. It contains a list of the
+                        repos together with versions. The versions can be
+                        specified using branches, tags, or hashes.
+default.xml           : This a time-invariant snapshot of manifest_template.xml.
+                        The difference is that all versions are specified as
+                        hashes.
+                        Auto-generated using manifest_template and data from
+                        the remotes.
author	Thomas Lundström <thomas.lundstrom@enea.com>	2016-04-13 10:00:11 +0200
committer	Thomas Lundström <thomas.lundstrom@enea.com>	2016-04-13 10:00:11 +0200
commit	2d8585e93fb4885a2e40c5dcac2e4484fa99ad7a (patch)
tree	6493e8e290b9be07a165a84fd8eade79f999379d
parent	bf70eca95171db379760fec43c072fcd14ecaaa7 (diff)
download	el_manifests-standard-2d8585e93fb4885a2e40c5dcac2e4484fa99ad7a.tar.gz

diff --git a/ls1021atwr/.README b/ls1021atwr/.README new file mode 100644 index 0000000..e3fdf1a --- /dev/null +++ b/ls1021atwr/.README
@@ -0,0 +1,9 @@
	1	This file is a template used to produce the real README. Read that one instead
	2
	3	________END_OF_HEADER________
	4
	5	Bla bla bla ...
	6
	7	________INSERT_BUILD_SEQUENCES_HERE________
	8
	9	________INSERT_BOOT_SEQUENCES_HERE________


diff --git a/ls1021atwr/README.first b/ls1021atwr/README.first new file mode 100644 index 0000000..6d08887 --- /dev/null +++ b/ls1021atwr/README.first
@@ -0,0 +1,27 @@
	1	This file contains the describing the manifest repo. Not to be confused with the
	2	file README.
	3
	4	The manifest repo contains:
	5
	6	README.first : This file
	7
	8	README : A README file that will be made available for the
	9	customer after repo sync. It contains build and boot
	10	commands and other specific info.
	11	Auto generated using .README and output from ELTF.
	12
	13	.README : A template for generating the README file. Currently,
	14	build and boot commands are provided by ELTF and they
	15	are integrated into .README to generate README. This is
	16	quite a mess, but the long term plan is to modify this
	17	in a way that makes the template obsolete.
	18
	19	manifest_template.xml : A template for default.xml. It contains a list of the
	20	repos together with versions. The versions can be
	21	specified using branches, tags, or hashes.
	22
	23	default.xml : This a time-invariant snapshot of manifest_template.xml.
	24	The difference is that all versions are specified as
	25	hashes.
	26	Auto-generated using manifest_template and data from
	27	the remotes.


diff --git a/p2041rdb/.README b/p2041rdb/.README new file mode 100644 index 0000000..e3fdf1a --- /dev/null +++ b/p2041rdb/.README
@@ -0,0 +1,9 @@
	1	This file is a template used to produce the real README. Read that one instead
	2
	3	________END_OF_HEADER________
	4
	5	Bla bla bla ...
	6
	7	________INSERT_BUILD_SEQUENCES_HERE________
	8
	9	________INSERT_BOOT_SEQUENCES_HERE________


diff --git a/p2041rdb/README.first b/p2041rdb/README.first new file mode 100644 index 0000000..6d08887 --- /dev/null +++ b/p2041rdb/README.first
@@ -0,0 +1,27 @@
	1	This file contains the describing the manifest repo. Not to be confused with the
	2	file README.
	3
	4	The manifest repo contains:
	5
	6	README.first : This file
	7
	8	README : A README file that will be made available for the
	9	customer after repo sync. It contains build and boot
	10	commands and other specific info.
	11	Auto generated using .README and output from ELTF.
	12
	13	.README : A template for generating the README file. Currently,
	14	build and boot commands are provided by ELTF and they
	15	are integrated into .README to generate README. This is
	16	quite a mess, but the long term plan is to modify this
	17	in a way that makes the template obsolete.
	18
	19	manifest_template.xml : A template for default.xml. It contains a list of the
	20	repos together with versions. The versions can be
	21	specified using branches, tags, or hashes.
	22
	23	default.xml : This a time-invariant snapshot of manifest_template.xml.
	24	The difference is that all versions are specified as
	25	hashes.
	26	Auto-generated using manifest_template and data from
	27	the remotes.


diff --git a/qemuarm/.README b/qemuarm/.README new file mode 100644 index 0000000..e3fdf1a --- /dev/null +++ b/qemuarm/.README
@@ -0,0 +1,9 @@
	1	This file is a template used to produce the real README. Read that one instead
	2
	3	________END_OF_HEADER________
	4
	5	Bla bla bla ...
	6
	7	________INSERT_BUILD_SEQUENCES_HERE________
	8
	9	________INSERT_BOOT_SEQUENCES_HERE________


diff --git a/qemuarm/README.first b/qemuarm/README.first new file mode 100644 index 0000000..6d08887 --- /dev/null +++ b/qemuarm/README.first
@@ -0,0 +1,27 @@
	1	This file contains the describing the manifest repo. Not to be confused with the
	2	file README.
	3
	4	The manifest repo contains:
	5
	6	README.first : This file
	7
	8	README : A README file that will be made available for the
	9	customer after repo sync. It contains build and boot
	10	commands and other specific info.
	11	Auto generated using .README and output from ELTF.
	12
	13	.README : A template for generating the README file. Currently,
	14	build and boot commands are provided by ELTF and they
	15	are integrated into .README to generate README. This is
	16	quite a mess, but the long term plan is to modify this
	17	in a way that makes the template obsolete.
	18
	19	manifest_template.xml : A template for default.xml. It contains a list of the
	20	repos together with versions. The versions can be
	21	specified using branches, tags, or hashes.
	22
	23	default.xml : This a time-invariant snapshot of manifest_template.xml.
	24	The difference is that all versions are specified as
	25	hashes.
	26	Auto-generated using manifest_template and data from
	27	the remotes.


diff --git a/qemuppc/.README b/qemuppc/.README new file mode 100644 index 0000000..e3fdf1a --- /dev/null +++ b/qemuppc/.README
@@ -0,0 +1,9 @@
	1	This file is a template used to produce the real README. Read that one instead
	2
	3	________END_OF_HEADER________
	4
	5	Bla bla bla ...
	6
	7	________INSERT_BUILD_SEQUENCES_HERE________
	8
	9	________INSERT_BOOT_SEQUENCES_HERE________


diff --git a/qemuppc/README.first b/qemuppc/README.first new file mode 100644 index 0000000..6d08887 --- /dev/null +++ b/qemuppc/README.first
@@ -0,0 +1,27 @@
	1	This file contains the describing the manifest repo. Not to be confused with the
	2	file README.
	3
	4	The manifest repo contains:
	5
	6	README.first : This file
	7
	8	README : A README file that will be made available for the
	9	customer after repo sync. It contains build and boot
	10	commands and other specific info.
	11	Auto generated using .README and output from ELTF.
	12
	13	.README : A template for generating the README file. Currently,
	14	build and boot commands are provided by ELTF and they
	15	are integrated into .README to generate README. This is
	16	quite a mess, but the long term plan is to modify this
	17	in a way that makes the template obsolete.
	18
	19	manifest_template.xml : A template for default.xml. It contains a list of the
	20	repos together with versions. The versions can be
	21	specified using branches, tags, or hashes.
	22
	23	default.xml : This a time-invariant snapshot of manifest_template.xml.
	24	The difference is that all versions are specified as
	25	hashes.
	26	Auto-generated using manifest_template and data from
	27	the remotes.


diff --git a/qemux86/.README b/qemux86/.README new file mode 100644 index 0000000..e3fdf1a --- /dev/null +++ b/qemux86/.README
@@ -0,0 +1,9 @@
	1	This file is a template used to produce the real README. Read that one instead
	2
	3	________END_OF_HEADER________
	4
	5	Bla bla bla ...
	6
	7	________INSERT_BUILD_SEQUENCES_HERE________
	8
	9	________INSERT_BOOT_SEQUENCES_HERE________


diff --git a/qemux86/README.first b/qemux86/README.first new file mode 100644 index 0000000..6d08887 --- /dev/null +++ b/qemux86/README.first
@@ -0,0 +1,27 @@
	1	This file contains the describing the manifest repo. Not to be confused with the
	2	file README.
	3
	4	The manifest repo contains:
	5
	6	README.first : This file
	7
	8	README : A README file that will be made available for the
	9	customer after repo sync. It contains build and boot
	10	commands and other specific info.
	11	Auto generated using .README and output from ELTF.
	12
	13	.README : A template for generating the README file. Currently,
	14	build and boot commands are provided by ELTF and they
	15	are integrated into .README to generate README. This is
	16	quite a mess, but the long term plan is to modify this
	17	in a way that makes the template obsolete.
	18
	19	manifest_template.xml : A template for default.xml. It contains a list of the
	20	repos together with versions. The versions can be
	21	specified using branches, tags, or hashes.
	22
	23	default.xml : This a time-invariant snapshot of manifest_template.xml.
	24	The difference is that all versions are specified as
	25	hashes.
	26	Auto-generated using manifest_template and data from
	27	the remotes.