From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: git and branches
Date: Thu, 09 Oct 2008 16:37:04 -0400 [thread overview]
Message-ID: <20081009203704.GA2490@denix.org> (raw)
In-Reply-To: <69E6C70090A0A14498CC98FAE5E06B6E3CF43D@hiob.intern.dresearch.de>
On Thu, Oct 09, 2008 at 11:39:18AM +0200, Sledz, Steffen wrote:
> As an OE beginner I'm a bit confused with the different branches. Is there an overview about all the branches available in the new git system. I made some searches in wiki.openembedded.net but could not found really helpful info.
>
> 'git branch -r' lists these branches:
>
> origin/HEAD
> origin/master
> origin/org.openembedded.dev
> origin/org.openembedded.documentation
> origin/org.openembedded.dreambox
> origin/org.openembedded.entity
> origin/org.openembedded.stable
> origin/org.openmoko.april-update
> origin/org.openmoko.dev
> origin/org.openmoko.xora.qtopia
> origin/org.openmoko.zecke.april-update
> origin/org.openmoko.zecke.autotools-bustage
> origin/org.openmoko.zecke.random-breakage
>
> <http://wiki.openembedded.net/index.php/DevelopmentBranches> lists these ones (without any description :( ):
>
> org.nslu2-linux.bitbake
> org.nslu2-linux.dev
> org.openembedded.dev
> org.openembedded.documentation
> org.openembedded.dreambox
> org.openembedded.oetest
> org.openembedded.oz354fam083
> org.openembedded.oz354x
> org.openembedded.packaged-staging
> org.openembedded.stable
>
> 'master' ist used as the default when getting the data with 'git clone git://git.openembedded.net/org.openembedded.dev' like described on <http://wiki.openembedded.net/index.php/Git#OpenEmbedded_Git_repository>. But what branch is 'master'? And which branches should one use for which purposes?
Please don't hijack threads - replying with the new Subject usually does not
create a new thread.
As was discussed earlier, master was just another name for
org.openembedded.dev branch, which is checked out now by default.
.dev is where all the latest development occurs, while .stable is the branch
supposedly good enough for production, i.e. for day to day use by end users.
--
Denys
next prev parent reply other threads:[~2008-10-09 20:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 5:51 ETA on git conversion Holger Freyther
2008-10-08 7:10 ` Khem Raj
2008-10-08 7:31 ` Tom Rini
2008-10-08 8:07 ` Koen Kooi
2008-10-08 10:52 ` Philip Balister
2008-10-08 10:56 ` Michael Krelin
2008-10-08 11:03 ` Holger Freyther
2008-10-08 11:18 ` Koen Kooi
2008-10-08 13:19 ` Leon Woestenberg
2008-10-08 13:32 ` Philip Balister
2008-10-08 15:57 ` Holger Freyther
2008-10-08 16:51 ` Michael Krelin
2008-10-08 16:54 ` Koen Kooi
2008-10-08 18:05 ` Philip Balister
2008-10-08 23:47 ` Rod Whitby
2008-10-09 9:39 ` git and branches Sledz, Steffen
2008-10-09 20:37 ` Denys Dmytriyenko [this message]
2008-10-09 22:31 ` Rod Whitby
2008-10-14 14:41 ` ETA on git conversion Jonas Bonn
2008-10-08 10:10 ` Marcin Juszkiewicz
2008-10-08 10:17 ` Koen Kooi
2008-10-08 13:06 ` Otavio Salvador
2008-10-14 14:12 ` Holger Freyther
2008-10-14 21:41 ` Holger Freyther
2008-10-15 0:29 ` Rodrigo Vivi
2008-10-15 2:17 ` Rod Whitby
2008-10-15 2:30 ` Rod Whitby
2008-10-15 9:31 ` Uli Luckas
2008-10-15 14:14 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081009203704.GA2490@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.