All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Müller-Klieser" <s.mueller-klieser@phytec.de>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/7] dangling patches
Date: Thu, 4 Aug 2016 16:52:36 +0200	[thread overview]
Message-ID: <57A356B4.7070109@phytec.de> (raw)
In-Reply-To: <CAJTo0LZ94KkvfRVUfq5cHFJ6tUKJs_JCMHWFYJACUDUHKg11_Q@mail.gmail.com>

On 04.08.2016 16:33, Burton, Ross wrote:
> On 4 August 2016 at 14:27, Stefan Müller-Klieser <
> s.mueller-klieser@phytec.de> wrote:
> 
>> There are some patches floating around with no reference to it. I guess
>> one just forgot to delete them during package upgrade. They should be
>> removed for consistency.
>>
> 
> I dont suppose you have tooling to find these, or was it manual review?

I found one and wrote a small bash script for the others, as it needs to
run outside of bitbake. Nothing special, though.
Stefan

> 
> Ross
> 


      reply	other threads:[~2016-08-04 14:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 13:27 [PATCH 0/7] dangling patches Stefan Müller-Klieser
2016-08-04 13:27 ` [PATCH 1/7] gstreamer1.0-plugins-bad: remove two " Stefan Müller-Klieser
2016-08-04 13:27 ` [PATCH 2/7] openssl: remove dangling patch Stefan Müller-Klieser
2016-08-04 13:27 ` [PATCH 3/7] guile: " Stefan Müller-Klieser
2016-08-04 13:27 ` [PATCH 4/7] python-numpy: " Stefan Müller-Klieser
2016-08-04 13:27 ` [PATCH 5/7] alsa-utils: " Stefan Müller-Klieser
2016-08-04 13:27 ` [PATCH 6/7] matchbox-desktop: " Stefan Müller-Klieser
2016-08-04 13:27 ` [PATCH 7/7] matchbox-panel-2: " Stefan Müller-Klieser
2016-08-04 14:33 ` [PATCH 0/7] dangling patches Burton, Ross
2016-08-04 14:52   ` Stefan Müller-Klieser [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=57A356B4.7070109@phytec.de \
    --to=s.mueller-klieser@phytec.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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.