From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: daisy branch for meta-openembedded, meta-qt5 / maintainer wanted
Date: Mon, 23 Jun 2014 13:01:43 +0200 [thread overview]
Message-ID: <20140623110143.GB2437@jama> (raw)
In-Reply-To: <53A7D3FE.30309@dresearch-fe.de>
[-- Attachment #1: Type: text/plain, Size: 1575 bytes --]
On Mon, Jun 23, 2014 at 09:15:10AM +0200, Steffen Sledz wrote:
> On 18.06.2014 16:34, Cliff Brake wrote:
> > On Wed, Jun 18, 2014 at 10:21 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> >> On Wed, Jun 18, 2014 at 10:04:52AM -0400, Cliff Brake wrote:
> >
> >>
> >>> Otavio, Armin, would you like me to add your emails to the maintainer
> >>> lists in these readme's as well?
> >>
> >> Should I wait 1 more day before merging branch above for possible
> >> maintainer additions?
> >
> > Yes, that would be a good idea. I'll send a pull request tomorrow, or
> > after I hear back from others.
> >
> > If there are other outstanding daisy patches, please let me know.
> >
> > As far as a procedure to merge changes, I propose that initially one
> > of the branch maintainers sends a pull request to the maillist .
> > Another maintainer ack the pull request, and then Martin (or other
> > main branch maintainer) merges and pushes. This will initially give
> > us a little bit more review. Eventually we may transition to one of
> > us pushing changes directly after co-maintainer ack. The goal is
> > obviously to keep daisy building and as stable as possible.
>
> Ping!
>
> My live555 patch is still waiting. :(
I've just merged it, but next time such patch needs to be merged in
master first (where it was merged by me on Saturday) and then
cherry-picked to release branch.
Otherwise we risk that some fix is only in release branch and the issue
stays in master.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-06-23 11:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 14:37 daisy branch for meta-openembedded, meta-qt5 / maintainer wanted Martin Jansa
[not found] ` <CAFeBWL5HuWex48xB_JZX_C7RMhzgfH93=AVJAkO7Qk7DUToFxg@mail.gmail.com>
2014-05-05 16:45 ` Martin Jansa
2014-05-07 18:32 ` Philip Balister
2014-05-11 14:53 ` Martin Jansa
2014-06-16 13:48 ` Martin Jansa
2014-06-17 20:55 ` Otavio Salvador
2014-06-18 1:32 ` Cliff Brake
2014-06-18 1:45 ` Cliff Brake
2014-06-18 11:27 ` Otavio Salvador
2014-06-18 14:04 ` Cliff Brake
2014-06-18 14:21 ` Martin Jansa
2014-06-18 14:34 ` Cliff Brake
2014-06-23 7:15 ` Steffen Sledz
2014-06-23 11:01 ` Martin Jansa [this message]
2014-06-23 11:13 ` Steffen Sledz
2014-06-18 15:20 ` Otavio Salvador
2014-06-18 16:41 ` akuster808
2014-05-11 23:03 ` Otavio Salvador
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=20140623110143.GB2437@jama \
--to=martin.jansa@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox