From: Darren Hart <dvhart@linux.intel.com>
To: Brian Hutchinson <b.hutchman@gmail.com>
Cc: yocto@yoctoproject.org, Chris Larson <clarson@kergoth.com>
Subject: Re: Moving angstrom under the yocto banner
Date: Tue, 03 Apr 2012 11:03:20 -0700 [thread overview]
Message-ID: <4F7B3B68.3040101@linux.intel.com> (raw)
In-Reply-To: <CAFZh4h947zMXK54SdSiHKFdo3eNXuCQtm3Wjk2g+t4zTBLbesw@mail.gmail.com>
On 04/03/2012 10:34 AM, Brian Hutchinson wrote:
> On Tue, Apr 3, 2012 at 1:26 PM, Chris Larson <clarson@kergoth.com> wrote:
>> I really don't see what the issue is here. If you want a stable
>> branch, we can look into creating such a thing upstream, though I'm
>> personally of the opinion that master should remain release-quality,
>> and make better use of feature branches, potentially a
>> next/integration branch for forthcoming features, than trying to
>> cherry pick onto a "stable" branch. There's nothing poky's structure
>> provides that can't also be provided via branching policy in the
>> individual repositories.
>
> I like what Chris said. I vote for this. It is standard SCM
> practice. All development goes on in a branch. Integration on
> another branch. When good enough, it is merged to master and tagged
> as a milestone release.
I'd really like to see this as well.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-04-03 18:04 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 18:44 Moving angstrom under the yocto banner Koen Kooi
2012-03-30 19:00 ` Osier-mixon, Jeffrey
2012-04-10 14:04 ` Koen Kooi
2012-04-10 16:07 ` Stewart, David C
2012-03-30 19:26 ` Mark Hatle
2012-03-30 19:33 ` Koen Kooi
2012-03-30 20:18 ` Mark Hatle
2012-03-30 20:33 ` Koen Kooi
2012-03-30 20:45 ` Tom Rini
2012-03-30 20:51 ` Koen Kooi
2012-03-30 20:55 ` Osier-mixon, Jeffrey
2012-03-30 21:02 ` Eric Bénard
2012-03-30 21:01 ` Osier-mixon, Jeffrey
2012-03-30 21:12 ` Koen Kooi
2012-03-30 21:11 ` Richard Purdie
2012-03-30 23:06 ` Stewart, David C
2012-03-30 23:09 ` Chris Larson
2012-03-30 23:14 ` Tom Rini
2012-03-30 23:49 ` Tom Rini
2012-03-30 23:58 ` Koen Kooi
2012-03-30 23:52 ` Darren Hart
2012-03-31 0:08 ` Koen Kooi
2012-03-31 0:28 ` Darren Hart
2012-03-31 0:53 ` Koen Kooi
2012-03-31 1:21 ` Darren Hart
2012-03-31 1:37 ` Koen Kooi
2012-03-31 2:27 ` Darren Hart
2012-03-31 3:00 ` Chris Larson
2012-03-31 3:27 ` Darren Hart
2012-03-31 7:06 ` Richard Purdie
2012-03-31 10:00 ` Frans Meulenbroeks
2012-04-02 4:08 ` Matthew McClintock
2012-04-02 11:27 ` Richard Purdie
2012-04-02 17:13 ` Tom Rini
2012-04-03 16:01 ` Darren Hart
2012-04-03 16:25 ` Martin Jansa
2012-04-03 16:32 ` Darren Hart
2012-04-03 16:40 ` Tom Rini
2012-04-03 17:07 ` Darren Hart
2012-04-03 16:44 ` Martin Jansa
2012-04-03 17:08 ` Darren Hart
2012-04-03 17:15 ` Tom Rini
2012-04-03 17:26 ` Chris Larson
2012-04-03 17:34 ` Brian Hutchinson
2012-04-03 18:03 ` Darren Hart [this message]
2012-03-31 16:30 ` Khem Raj
2012-04-01 0:51 ` Chris Larson
2012-03-31 15:37 ` Paul Eggleton
-- strict thread matches above, loose matches on Subject: below --
2012-03-30 22:32 Daniel Lazzari
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=4F7B3B68.3040101@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=b.hutchman@gmail.com \
--cc=clarson@kergoth.com \
--cc=yocto@yoctoproject.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.