Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Randy MacLeod <randy.macleod@windriver.com>
To: Ruslan Bilovol <ruslan.bilovol@gmail.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/6] Remove lost patches from oe-core
Date: Wed, 30 Jan 2019 18:19:22 -0500	[thread overview]
Message-ID: <9aaf65ce-c4d2-c9ef-24bb-e85bf667bd9c@windriver.com> (raw)
In-Reply-To: <1548507480-22805-1-git-send-email-ruslan.bilovol@gmail.com>

On 1/26/19 7:57 AM, Ruslan Bilovol wrote:
> Working with recent oe-core I noticed that there are
> patches not used by any recipe, which is confusing.
> This is caused by mistakes in recipe upgrades, when
> people remove patch from SRC_URI but forgets to
> delete actual patch.
> Instead of fixing only recipes I worked on,
> I wrote a simple bash script which found all 6
> lost patches in oe-core.


What's the 'simple bash script' ?
We could add it to scripts and use it later and for other layers.

-- 
# Randy MacLeod
# Wind River Linux


      parent reply	other threads:[~2019-01-30 23:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26 12:57 [PATCH 0/6] Remove lost patches from oe-core Ruslan Bilovol
2019-01-26 12:57 ` [PATCH 1/6] lttng: drop lost patch Ruslan Bilovol
2019-01-26 12:57 ` [PATCH 2/6] bind: " Ruslan Bilovol
2019-01-26 12:57 ` [PATCH 3/6] dhcp: " Ruslan Bilovol
2019-01-26 12:57 ` [PATCH 4/6] connman: " Ruslan Bilovol
2019-01-26 12:57 ` [PATCH 5/6] subversion: " Ruslan Bilovol
2019-01-26 12:58 ` [PATCH 6/6] perl: " Ruslan Bilovol
2019-01-30 23:19 ` Randy MacLeod [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=9aaf65ce-c4d2-c9ef-24bb-e85bf667bd9c@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ruslan.bilovol@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox