From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lpp01m020-f176.google.com (mail-lpp01m020-f176.google.com [209.85.217.176]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id E2C3EE0044D for ; Wed, 8 Feb 2012 11:23:59 -0800 (PST) Received: by lboi15 with SMTP id i15so596401lbo.35 for ; Wed, 08 Feb 2012 11:23:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=zZO5aWd/XBJTX6O60l4OIyZjavLaGk4U/dw+smwXtdg=; b=twfElWUPiQ8Tp8vsx3mVce8CVw+EDRfQLzRZXulIv0FDdG+wHxK7HE170BaIX4qfCx aCwFZqBb6eINfbNMNowXJ92IplG1kLatGAo9qUpX4MJPvOZk/eC3Vh5cK19P/Eob/tjr uIABo01SJvS82N2DyJJPWVo4T7EZ6hdfTi63U= Received: by 10.112.28.169 with SMTP id c9mr8214157lbh.42.1328729038604; Wed, 08 Feb 2012 11:23:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.152.5.201 with HTTP; Wed, 8 Feb 2012 11:23:27 -0800 (PST) In-Reply-To: <20120208100718.GB8335@giant> References: <4F323C52.8030304@intel.com> <20120208100718.GB8335@giant> From: Khem Raj Date: Wed, 8 Feb 2012 11:23:27 -0800 Message-ID: To: =?UTF-8?Q?Bj=C3=B6rn_Stenberg?= Cc: Yocto Project Discussion Subject: Re: Upstream-Status finally @ 100% X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2012 19:24:00 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, Feb 8, 2012 at 2:07 AM, Bj=C3=B6rn Stenberg wrote: > Who sets the Upstream-Status? Are there guidelines how to do it? > patch author importer whoever brings this patch in into oe. Sometimes there might be judgement error on patches thats why I said "for most of them it reflects the status of patch w.r.t. upstream" > I spoke to the author of curl and mentioned the two patches in Yocto agai= nst it, both of which are marked as "Upstream-Status: Inappropriate". He sa= id those patches were never submitted to him. > > Are we dismissing patches without even giving upstream a chance to commen= t? Thats not the intention at all. All patches should go upstream from OE's POV it would be cool to have 0 patches locally If someone had better insights into patches and submit more appropriate analysis of patches thats welcome all the time.