All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] binutils-2.20: remove unneeded/unwanted patches
Date: Sat, 12 Dec 2009 12:49:33 +0100	[thread overview]
Message-ID: <20091212114933.GA8391@mx.loc> (raw)
In-Reply-To: <19c1b8a90912092039w592aed8btf658721b77f8e646@mail.gmail.com>

On Wed, Dec 09, 2009 at 08:39:20PM -0800, Khem Raj wrote:
>On Wed, Dec 9, 2009 at 1:24 PM, Bernhard Reutner-Fischer
><rep.dot.nop@gmail.com> wrote:
>> Hi khem,
>>
>> In 33630af91d1027a91b43f697c86e809a770668e1 you (AFAICS) added
>> binutils-2.20 support, yet the hunks mentioned below were already
>> applied or are unneeded in that release?! How did you patch/compile
>> this, perhaps i'm missing some crucial part in the setup?
>> Thanks for clarification/fixing this up,
>
>out of these three only patch which is applied right now is
>binutils-arm-pr7093.patch and by nature of the patch it adds a check
>and returns if true. Now that the patch it applied twice the check is done twice
>making one redundant but not incorrect. Just existence of patch does not apply
>them automatically you have to add the patches to SRC_URI in order to include
>them.

I'm aware of this, yes. But the fact that you pulled them into the 2.20
patchdir suggested that they were somehow still of interrest for that
version, although not applied.
>
>I will remove these patches from repo as they are not applied.

Thanks alot for removing them, they're just taking up space and
bandwidth.

cheers,



      reply	other threads:[~2009-12-12 11:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 21:24 [PATCH] binutils-2.20: remove unneeded/unwanted patches Bernhard Reutner-Fischer
2009-12-10  4:39 ` Khem Raj
2009-12-12 11:49   ` Bernhard Reutner-Fischer [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=20091212114933.GA8391@mx.loc \
    --to=rep.dot.nop@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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.