All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Joslyn <robert.joslyn@redrectangle.org>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [pyro][PATCH] openssl: Update from 1.0.2n to 1.0.2p
Date: Wed, 31 Oct 2018 22:39:22 -0700	[thread overview]
Message-ID: <1541050762.8937.20.camel@redrectangle.org> (raw)
In-Reply-To: <CAJ86T=W08p366z458VjejjFkVTTFu23o9U2o6utp027a0p7r9w@mail.gmail.com>

On Wed, 2018-10-31 at 20:31 -0700, Andre McCurdy wrote:
> On Wed, Oct 31, 2018 at 7:54 PM Robert Joslyn
> <robert.joslyn@redrectangle.org> wrote:
> > 
> > Refresh parallel.patch.
> > 
> > Remove duplicate LIC_FILES_CHKSUM assignment.
> > 
> > License-Update: Updated copyright years
> 
> Normally a backport to pyro would be merged to sumo and rocko first,
> so this would be done in steps:
> 
> 1) Backport the existing patches to update 1.0.2n -> 1.0.2o from
> rocko to pyro
> 
> 2) Update rocko from 1.0.2o -> 1.0.2p, ideally by backporting patches
> already in sumo. Note however that the update to 1.0.2p in sumo comes
> with a lot of non-critical cleanups and it's questionable how far
> back
> we want to port those, so a new patch which just updates the version
> might be preferred?
> 
> 3) Backport whatever 1.0.2o -> 1.0.2p patches are merged to rocko
> into pyro.

I debated how much to backport from sumo, and thought I would try to
minimize the changes to the rocko and pyro branches. The two patches I
sent are pretty much the minimum required to get 1.0.2p working with
rocko and pyro.

It's probably easiest to take what's on sumo directly back to rocko and
then pyro. I'll test that tomorrow and resend the patches if there's no
objection to taking the other small fixes. I have a feeling trying to
pull out small cleanups is more trouble than it's worth (for my
purposes at least), but I'll do so if that's preferred.

Thanks,
Robert


  reply	other threads:[~2018-11-01  5:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01  2:53 [pyro][PATCH] openssl: Update from 1.0.2n to 1.0.2p Robert Joslyn
2018-11-01  3:31 ` Andre McCurdy
2018-11-01  5:39   ` Robert Joslyn [this message]
2018-11-01  6:20     ` Andre McCurdy

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=1541050762.8937.20.camel@redrectangle.org \
    --to=robert.joslyn@redrectangle.org \
    --cc=armccurdy@gmail.com \
    --cc=openembedded-core@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.