Re: [meta-networking][PATCH v2] cyassl: add version 3.3.0, remove version 3.1.0

[Martin Jansa <martin.jansa@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 7275 bytes --]

On Mon, Dec 29, 2014 at 06:45:23PM -0500, Joe MacDonald wrote:
> [Re: [oe] [meta-networking][PATCH v2] cyassl: add version 3.3.0, remove version 3.1.0] On 14.12.29 (Mon 14:41) Joe MacDonald wrote:
> 
> > [Re: [oe] [meta-networking][PATCH v2] cyassl: add version 3.3.0, remove version 3.1.0] On 14.12.29 (Mon 20:27) Martin Jansa wrote:
> > 
> > > On Mon, Dec 29, 2014 at 01:59:21PM -0500, Joe MacDonald wrote:
> > > > Hey Martin,
> > > > 
> > > > [Re: [oe] [meta-networking][PATCH v2] cyassl: add version 3.3.0, remove version 3.1.0] On 14.12.29 (Mon 19:53) Martin Jansa wrote:
> > > > 
> > > > > On Mon, Dec 29, 2014 at 11:50:30AM -0700, Leah wrote:
> > > > > > I was just wondering if this commit was recieved and/or approved?
> > > > > 
> > > > > Received and not yet approved, look at master-next branch.
> > > > 
> > > > I generally try to send out a message when I merge anything to
> > > > master-next so as to let the submitter know it's been merged.  I do seem
> > > > to be in the minority, but if possible it would also help me out if you
> > > > could send an ack when you merge something for meta-networking into
> > > > master so I know I can remove it from my working queue.  That usually
> > > > only pops up when I've been offline for a few weeks, but it would really
> > > > help with managing the mail queue.
> > > 
> > > You mean when you merge it to master not master-next, right?
> > 
> > Yeah, of course.  master-next gets so many updates I don't think mail
> > about integration there would be really useful for anyone nor a
> > particularly good use of your time.
> > 
> > > I usually merge meta-networking changes to master-next only to include
> > > them in next jenkins build and then leave them to you to merge them to
> > > master when you want (unless I'm reporting build failures caused by
> > > them).
> > 
> > Yep, I know.  It's very infrequent I run into any new recipes in master.
> > That is why I have the occasional 'huh' moment when I'm walking through
> > the mail queue, see something new, check master-next for something to
> > cherry-pick and find it's already in master.  If I'm trying to clear out
> > a backlog, though, just knowing which threads I don't even need to look
> > at is a win, for sure.
> > 
> > > All merges to master-next are indicated by master-next bundle on
> > > patchwork (and Archived status)
> > > http://www.openembedded.org/wiki/Patchwork#Multiple_layers_sharing_the_same_oe_project_on_patchwork
> > > 
> > > I would like more people updating status of their patches on patchwork,
> > > that includes you marking merged meta-networking patches. After updating
> > > 6 cyassl patches on patchwork I don't want to also send another batch of
> > > e-mails for the amount of patches going into meta-oe, meta-smartphone,
> > > meta-qt5 repos.
> > 
> > Understood.  I haven't looked at patchworks in quite some time because I
> > was frequently seeing patches on the mailing list that weren't showing
> > up there and that didn't seem particularly efficient if everything was
> > in my mailbox but some smaller set were in my patchworks queue.  I'll
> > make more of an effort to pay attention to it and update status there as
> > well.
> 
> So I took a bit of time this evening and cleaned out the meta-networking
> patch queue here:
> 
> http://patchwork.openembedded.org/project/oe/list/?state=1&q=meta-networking&archive=both
> 
> I didn't touch the 'dizzy' patches, but other than that I think it now
> accurately reflects the state of "not-yet-merged"-ness for master.
> There's four patches outstanding there will probably be merged (or
> otherwise processed) in the next day or so.

Thanks, now I can add meta-networking patches to meta-networking bundle
instead of master-next (even when I will also include them in
master-next branch).

> > -J.
> > 
> > > 
> > > Regards,
> > > 
> > > > > > On Mon, Dec 22, 2014 at 2:29 PM, lchristina26 <lchristina26@hotmail.com>
> > > > > > wrote:
> > > > > > 
> > > > > > > Signed-off-by: Leah <lchristina26@hotmail.com>
> > > > > > > ---
> > > > > > >  .../cyassl/{cyassl_3.1.0.bb => cyassl_3.3.0.bb}                    | 7
> > > > > > > ++++---
> > > > > > >  1 file changed, 4 insertions(+), 3 deletions(-)
> > > > > > >  rename meta-networking/recipes-connectivity/cyassl/{cyassl_3.1.0.bb =>
> > > > > > > cyassl_3.3.0.bb} (74%)
> > > > > > >
> > > > > > > diff --git a/meta-networking/recipes-connectivity/cyassl/cyassl_3.1.0.bb
> > > > > > > b/meta-networking/recipes-connectivity/cyassl/cyassl_3.3.0.bb
> > > > > > > similarity index 74%
> > > > > > > rename from meta-networking/recipes-connectivity/cyassl/cyassl_3.1.0.bb
> > > > > > > rename to meta-networking/recipes-connectivity/cyassl/cyassl_3.3.0.bb
> > > > > > > index e3edab6..b6f852d 100644
> > > > > > > --- a/meta-networking/recipes-connectivity/cyassl/cyassl_3.1.0.bb
> > > > > > > +++ b/meta-networking/recipes-connectivity/cyassl/cyassl_3.3.0.bb
> > > > > > > @@ -1,4 +1,4 @@
> > > > > > > -SUMMARY = "CyaSSL Embedded SSL Library"
> > > > > > > +SUMMARY = "CyaSSL Lightweight, Embedded SSL Library"
> > > > > > >  DESCRIPTION = "CyaSSL is a lightweight SSL library written in C and \
> > > > > > >                 optimized for embedded and RTOS environments. It can be \
> > > > > > >                 Up to 20 times smaller than OpenSSL while still supporting
> > > > > > > \
> > > > > > > @@ -11,7 +11,8 @@ LIC_FILES_CHKSUM =
> > > > > > > "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
> > > > > > >
> > > > > > >  SRC_URI = "http://www.yassl.com/${BP}.zip"
> > > > > > >
> > > > > > > -SRC_URI[md5sum] = "72477eb50697e759d309c49cb1aef18a"
> > > > > > > -SRC_URI[sha256sum] =
> > > > > > > "85a79009d2a7468910dfb1e4b975e0b00a42c695f4f1a2adc16d2507b5d0b03e"
> > > > > > > +SRC_URI[md5sum] = "0303eb0f2f9065a1207d9104ab0eba7c"
> > > > > > > +SRC_URI[sha256sum] =
> > > > > > > "e51583ea1e4d64537553922d67a96360312811dffef58d4c05506aa98a296fe3"
> > > > > > >
> > > > > > >  inherit autotools
> > > > > > > +
> > > > > > > --
> > > > > > > 1.9.1
> > > > > > >
> > > > > > > --
> > > > > > > _______________________________________________
> > > > > > > Openembedded-devel mailing list
> > > > > > > Openembedded-devel@lists.openembedded.org
> > > > > > > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> > > > > > >
> > > > > > >
> > > > > > 
> > > > > > 
> > > > > > -- 
> > > > > > 
> > > > > > Leah Thompson
> > > > > > www.wolfssl.com
> > > > > > leah@wolfssl.com
> > > > > > 406-570-1389
> > > > > > Skype: lchristina26
> > > > > > -- 
> > > > > > _______________________________________________
> > > > > > Openembedded-devel mailing list
> > > > > > Openembedded-devel@lists.openembedded.org
> > > > > > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> > > > > 
> > > > > -- 
> > > > > Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com
> > > > 
> > > > 
> > > > 
> > > > -- 
> > > > -Joe MacDonald.
> > > > :wq
> > > 
> > > 
> > > 
> > -- 
> > -Joe MacDonald.
> > :wq
> 
> 
> 
> -- 
> -Joe MacDonald.
> :wq



-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]