From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: Denys Dmytriyenko <denys@ti.com>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [dora][PATCH] opkg-utils: Update to latest git master
Date: Sun, 06 Apr 2014 16:50:17 +0100 [thread overview]
Message-ID: <1396799417.24597.19.camel@ted> (raw)
In-Reply-To: <CANyK_8d+pAHXhtdPUYVaZNJe+eOnyATd9cCWXHxgG3mVxrbeeA@mail.gmail.com>
On Sun, 2014-04-06 at 16:42 +0100, Paul Barker wrote:
> On 3 April 2014 23:32, Martin Jansa <martin.jansa@gmail.com> wrote:
> >
> > I haven't read whole discussion, but the idea of adding just one needed
> > patch from the repo into oe-core metadata seems reasonable to me (unless
> > someone wants to create dora branch in opkg-utils repo and cherry-pick
> > just that one required commit there + update SRC_URI + SRCREV
> > accordingly).
>
> I'd rather not keep a 'dora' branch in opkg-utils as I'd like it to
> align with opkg and be independent of which build system is being
> used. I think putting the patch into the dora branch of oe-core is the
> best way forward as the change in question is tiny.
In this specific case I'd tend to agree FWIW...
Cheers,
Richard
prev parent reply other threads:[~2014-04-06 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 0:58 [dora][PATCH] opkg-utils: Update to latest git master Denys Dmytriyenko
2014-04-01 12:29 ` Paul Barker
2014-04-01 13:04 ` Paul Barker
2014-04-03 14:17 ` Robert Yang
2014-04-03 16:23 ` Denys Dmytriyenko
2014-04-03 22:32 ` Martin Jansa
2014-04-06 15:42 ` Paul Barker
2014-04-06 15:50 ` Richard Purdie [this message]
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=1396799417.24597.19.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=denys@ti.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
/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