2011.03-maintenance - Revision history

Trini: Spell out that oe-core / meta-oe / etc is a fine place for changes to be backported from rather than a strict cherry-pick

2011-06-16T21:10:25Z

Spell out that oe-core / meta-oe / etc is a fine place for changes to be backported from rather than a strict cherry-pick

← Older revision		Revision as of 21:10, 16 June 2011
Line 24:		Line 24:
	= Dealing with changes =		= Dealing with changes =

	This branch is being run on a 'pull model' where in all changes will be pushed into the branch by [[Talk:trini\|Tom Rini]]. Changes may be submitted via the openembedded-devel mailing list as patches or as '''git pull''' requests to branches that reside in some publicly available git tree. Unless specific to code that no longer resides in a non-maintenance branch (ie master here or oe-core / meta-oe / etc) code must be a backport and should say where the code already resides (for ease of review, interoperability checking and so forth). Requests should have '''[2011.03-maintenance]''' in the subject line. To give others time to comment, pull requests will usually have a day between being posted and being pulled.		This branch is being run on a 'pull model' where in all changes will be pushed into the branch by [[Talk:trini\|Tom Rini]]. Changes may be submitted via the openembedded-devel mailing list as patches or as '''git pull''' requests to branches that reside in some publicly available git tree. This pull request should include a log of the changes, but that is not strictly required. Unless specific to code that no longer resides in a non-maintenance branch (ie master here or oe-core / meta-oe / etc) code must be a backport and should say where the code already resides (for ease of review, interoperability checking and so forth). Changes may reside in either the openembedded 'master' repository OR a relevant public layer in the oe-core / meta-oe / etc universe. Requests should have '''[2011.03-maintenance]''' in the subject line. To give others time to comment, pull requests will usually have a day between being posted and being pulled.

	== What is supported ==		== What is supported ==

Trini: Note a 1d delay before pulling

2011-05-03T15:15:33Z

Note a 1d delay before pulling

← Older revision		Revision as of 15:15, 3 May 2011
Line 24:		Line 24:
	= Dealing with changes =		= Dealing with changes =

	This branch is being run on a 'pull model' where in all changes will be pushed into the branch by [[Talk:trini\|Tom Rini]]. Changes may be submitted via the openembedded-devel mailing list as patches or as '''git pull''' requests to branches that reside in some publicly available git tree. Unless specific to code that no longer resides in a non-maintenance branch (ie master here or oe-core / meta-oe / etc) code must be a backport and should say where the code already resides (for ease of review, interoperability checking and so forth). Requests should have '''[2011.03-maintenance]''' in the subject line.		This branch is being run on a 'pull model' where in all changes will be pushed into the branch by [[Talk:trini\|Tom Rini]]. Changes may be submitted via the openembedded-devel mailing list as patches or as '''git pull''' requests to branches that reside in some publicly available git tree. Unless specific to code that no longer resides in a non-maintenance branch (ie master here or oe-core / meta-oe / etc) code must be a backport and should say where the code already resides (for ease of review, interoperability checking and so forth). Requests should have '''[2011.03-maintenance]''' in the subject line. To give others time to comment, pull requests will usually have a day between being posted and being pulled.


	== What is supported ==		== What is supported ==

Trini: /* What is supported */

2011-03-09T18:55:23Z

What is supported

← Older revision		Revision as of 18:55, 9 March 2011
Line 34:		Line 34:
	! '''Distribution''' !! '''Machines''' !! '''Image / Feed / etc target'''		! '''Distribution''' !! '''Machines''' !! '''Image / Feed / etc target'''
	\|-		\|-
	\| angstrom-2008.1 \|\| beagleboard, bug20, hawkboard, am180x-evm, am3517-evm, am37x-evm, am389x-evm, c6a816x-evm, da830-omapl137-evm, da850-omapl138-evm, dm355-evm, dm357-evm, dm365-evm, dm37x-evm, dm6446-evm, dm6467-evm, dm6467t-evm, omap3evm, qemuarm, qemumips, qemuppc, qemux86, efika \|\| ?		\| angstrom-2008.1 \|\| beagleboard, bug20, hawkboard, am180x-evm, am3517-evm, am37x-evm, am389x-evm, c6a816x-evm, da830-omapl137-evm, da850-omapl138-evm, dm355-evm, dm357-evm, dm365-evm, dm37x-evm, dm6446-evm, dm6467-evm, dm6467t-evm, omap3evm, qemuarm, qemumips, qemuppc, qemux86, efika \|\| console-image, angstrom-gnome-image
	\|}		\|}

	If you would like to see something else supported please speak up and volunteer to support it.		If you would like to see something else supported please speak up and volunteer to support it.

Stefan: /* What is supported */

2011-03-09T16:19:56Z

What is supported

← Older revision		Revision as of 16:19, 9 March 2011
Line 34:		Line 34:
	! '''Distribution''' !! '''Machines''' !! '''Image / Feed / etc target'''		! '''Distribution''' !! '''Machines''' !! '''Image / Feed / etc target'''
	\|-		\|-
	\| angstrom-2008.1 \|\| beagleboard, hawkboard, am180x-evm, am3517-evm, am37x-evm, am389x-evm, c6a816x-evm, da830-omapl137-evm, da850-omapl138-evm, dm355-evm, dm357-evm, dm365-evm, dm37x-evm, dm6446-evm, dm6467-evm, dm6467t-evm, omap3evm, qemuarm, qemumips, qemuppc, qemux86, efika \|\| ?		\| angstrom-2008.1 \|\| beagleboard, bug20, hawkboard, am180x-evm, am3517-evm, am37x-evm, am389x-evm, c6a816x-evm, da830-omapl137-evm, da850-omapl138-evm, dm355-evm, dm357-evm, dm365-evm, dm37x-evm, dm6446-evm, dm6467-evm, dm6467t-evm, omap3evm, qemuarm, qemumips, qemuppc, qemux86, efika \|\| ?
	\|}		\|}

	If you would like to see something else supported please speak up and volunteer to support it.		If you would like to see something else supported please speak up and volunteer to support it.

Trini: /* Dealing with changes */

2011-03-09T16:06:21Z

Dealing with changes

← Older revision		Revision as of 16:06, 9 March 2011
Line 24:		Line 24:
	= Dealing with changes =		= Dealing with changes =

	This branch is being run on a 'pull model' where in all changes will be pushed into the branch by [[Talk:trini\|Tom Rini]]. Changes may be submitted via the openembedded-devel mailing list as patches or as =git pull= requests to branches that reside in some publicly available git tree. Unless specific to code that no longer resides in a non-maintenance branch (ie master here or oe-core / meta-oe / etc) code must be a backport and should say where the code already resides (for ease of review, interoperability checking and so forth). Requests should have '''[2011.03-maintenance]''' in the subject line.		This branch is being run on a 'pull model' where in all changes will be pushed into the branch by [[Talk:trini\|Tom Rini]]. Changes may be submitted via the openembedded-devel mailing list as patches or as '''git pull''' requests to branches that reside in some publicly available git tree. Unless specific to code that no longer resides in a non-maintenance branch (ie master here or oe-core / meta-oe / etc) code must be a backport and should say where the code already resides (for ease of review, interoperability checking and so forth). Requests should have '''[2011.03-maintenance]''' in the subject line.

Trini: /* Dealing with changes */

2011-03-09T16:03:27Z

Dealing with changes

← Older revision		Revision as of 16:03, 9 March 2011
Line 24:		Line 24:
	= Dealing with changes =		= Dealing with changes =

	This branch is being run on a 'pull model' where in all changes will be pushed into the branch by [[Talk:trini\|Tom Rini]]. Changes may be submitted via the openembedded-devel mailing list as patches or as =git pull= requests to branches that reside in some publicly available git tree. Unless specific to code that no longer resides in a non-maintenance branch (ie master here or oe-core / meta-oe / etc) code must be a backport and should say where the code already resides (for ease of review, interoperability checking and so forth).		This branch is being run on a 'pull model' where in all changes will be pushed into the branch by [[Talk:trini\|Tom Rini]]. Changes may be submitted via the openembedded-devel mailing list as patches or as =git pull= requests to branches that reside in some publicly available git tree. Unless specific to code that no longer resides in a non-maintenance branch (ie master here or oe-core / meta-oe / etc) code must be a backport and should say where the code already resides (for ease of review, interoperability checking and so forth). Requests should have '''[2011.03-maintenance]''' in the subject line.

Trini: /* What is supported */

2011-03-09T16:01:53Z

What is supported

← Older revision		Revision as of 16:01, 9 March 2011
Line 34:		Line 34:
	! '''Distribution''' !! '''Machines''' !! '''Image / Feed / etc target'''		! '''Distribution''' !! '''Machines''' !! '''Image / Feed / etc target'''
	\|-		\|-
	\| angstrom-2008.1 \|\| ? \|\| ?		\| angstrom-2008.1 \|\| beagleboard, hawkboard, am180x-evm, am3517-evm, am37x-evm, am389x-evm, c6a816x-evm, da830-omapl137-evm, da850-omapl138-evm, dm355-evm, dm357-evm, dm365-evm, dm37x-evm, dm6446-evm, dm6467-evm, dm6467t-evm, omap3evm, qemuarm, qemumips, qemuppc, qemux86, efika \|\| ?
	\|}		\|}

	If you would like to see something else supported please speak up and volunteer to support it.		If you would like to see something else supported please speak up and volunteer to support it.

Trini: Created page with ''''Definition:''' The 2011.03-maintenance branch is a branch made based on the Release-2011.03 release tag in the metadata. = Getting the stable branch = F…'

2011-03-09T15:29:07Z

Created page with ''''Definition:''' The 2011.03-maintenance branch is a branch made based on the Release-2011.03 release tag in the metadata. = Getting the stable branch = F…'

New page

'''Definition:''' The 2011.03-maintenance branch is a branch made based on the [[release-2011.03|Release-2011.03]] release tag in the metadata.

= Getting the stable branch =

First download the main branch in the usual way

git clone git://git.openembedded.org/openembedded

then take a look at available branches in the main repository

git branch -a

now you can get the stable branch with

git checkout -b 2011.03-maintenance origin/2011.03-maintenance

and verify the branch where you are working now

$ git branch
master
* 2011.03-maintenance

= Dealing with changes =

This branch is being run on a 'pull model' where in all changes will be pushed into the branch by [[Talk:trini|Tom Rini]]. Changes may be submitted via the openembedded-devel mailing list as patches or as =git pull= requests to branches that reside in some publicly available git tree. Unless specific to code that no longer resides in a non-maintenance branch (ie master here or oe-core / meta-oe / etc) code must be a backport and should say where the code already resides (for ease of review, interoperability checking and so forth).

== What is supported ==

The following combinations are supported by volunteers in this branch:

{| class="sortable" border="1"
! '''Distribution''' !! '''Machines''' !! '''Image / Feed / etc target'''
|-
| angstrom-2008.1 || ? || ?
|}

If you would like to see something else supported please speak up and volunteer to support it.