All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Daniel Stenberg <daniel@haxx.se>
Cc: Yocto Project Discussion <yocto@yoctoproject.org>
Subject: Re: Upstream-Status finally @ 100%
Date: Wed, 08 Feb 2012 15:18:43 -0800	[thread overview]
Message-ID: <4F3302D3.7070507@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1202082215320.8688@tvnag.unkk.fr>

On 02/08/2012 01:26 PM, Daniel Stenberg wrote:
> On Wed, 8 Feb 2012, Saul Wold wrote:
>
>> If the author of curl would like to review and/or implement
>> modification for OE that would be awesome, feel free to share the
>> patches with them.
>
> I am the maintainer of curl.
>
> The curl patches Björn mentioned are clearly not written in way intended
> to be "upstreamable" so they cannot be accepted by the curl project and
> nobody has tried to.
>
I am sure there are many patches like that in OE, they are written, 
tested and then forgotten about, our goal here is to not let them get 
forgotten.

> This said, at least one of the patches fixes a problem that still exists
> upstream but the yocto patch [*] is made in such a hard-coded way it'd
> have to be seriously edited to get accepted. The flaw has not even been
> discussed with or mentioned to the curl project AFAICR...
>
> So, room for improvements!
>
> [*] =
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-support/curl/curl/noldlibpath.patch
>
>

Daniel,

I think Khem has already said that we are taking incremental steps here, 
as I mentioned in my prior email, we have over 1200 patches lurking 
around in OE currently, initially we have about 460 as marked as pending.

If you can fix those issues, since we can't address all of them 
initially or be experts in all upstreams, we would be very grateful to 
remove 1 or 2 more patches.

Thanks for your understanding.

Sau!


  parent reply	other threads:[~2012-02-08 23:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08  9:11 Upstream-Status finally @ 100% Saul Wold
2012-02-08  9:11 ` Saul Wold
2012-02-08 10:07 ` Björn Stenberg
2012-02-08 18:57   ` Saul Wold
2012-02-08 21:26     ` Daniel Stenberg
2012-02-08 21:34       ` Khem Raj
2012-02-08 23:18       ` Saul Wold [this message]
2012-02-09  9:26         ` Daniel Stenberg
2012-02-09 12:22         ` Koen Kooi
2012-02-09 12:30           ` Paul Eggleton
2012-02-09 14:51             ` Koen Kooi
2012-02-09 15:31               ` Paul Eggleton
2012-02-09 17:39                 ` Saul Wold
2012-02-09 14:46           ` Khem Raj
2012-02-08 19:23   ` Khem Raj
2012-02-08 17:07 ` Stewart, David C
2012-02-08 17:34   ` Osier-mixon, Jeffrey
2012-02-08 17:37     ` Paul Eggleton
2012-02-08 17:37       ` [yocto] " Paul Eggleton
2012-02-08 17:45     ` Khem Raj
2012-02-08 17:45       ` [yocto] " Khem Raj
2012-02-08 18:04       ` Osier-mixon, Jeffrey
2012-02-08 18:45         ` Saul Wold
2012-02-08 18:45           ` [yocto] " Saul Wold
2012-02-08 21:44           ` [OE-core] " Paul Menzel
2012-02-08 21:44             ` Paul Menzel

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=4F3302D3.7070507@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=daniel@haxx.se \
    --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.