All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Müller" <schnitzeltony@gmail.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH 00/17] remove gnome2 recipes for discontinued projects
Date: Tue, 20 Mar 2018 19:03:57 +0100	[thread overview]
Message-ID: <CALbNGRStZxv6Mt3phdup6dJ-jNMHsMRNNodBJP9mSjMx62P4rg@mail.gmail.com> (raw)
In-Reply-To: <6d77f84f-1808-b929-7719-7fef10bc11b4@linux.intel.com>

On Tue, Mar 20, 2018 at 11:18 AM, Alexander Kanavin
<alexander.kanavin@linux.intel.com> wrote:
> On 03/19/2018 10:28 PM, Andreas Müller wrote:
>>
>> I can't stand the low-quality/split/maintainer-spam anymore: Guys one way
>> to
>> change things is start sending patches.
>
>
> Yes, yes, yes. And yes. Even more could be removed, e.g. libunique and
> everything that wants it. I'll look when I have a bit of time.
>
> Alex
You are invited :)

Off-Topic:
Today I changed to master builds and started fixing the patch-fuzz-thingy.

* Thanks for doing that
* This is a perfect advertisement for devtool - have not yet used
before. Am not sure if I am going to use that for daily recipe
handling but for this task it is VERY helpful. Together with with git
add -p the diff can be kept readable. There are two 'bugs' I found:

1. If I am not mistaken it creates wrong file path when using
'patchdir' - sorry but I forgot where it was
2. An interesting case is mariadb-native/fix-cmake-module-path.patch
(current meta-openembedded master / meta-oe): Although the patch moves
just one line, devtool creates a heavy monster diff - have no idea why

Andreas


  reply	other threads:[~2018-03-20 18:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 20:28 [PATCH 00/17] remove gnome2 recipes for discontinued projects Andreas Müller
2018-03-19 20:28 ` [PATCH 01/17] libglade: remove Andreas Müller
2018-03-19 20:28 ` [PATCH 02/17] evolution-data-server: remove libglade from dependencies Andreas Müller
2018-03-19 20:28 ` [PATCH 03/17] libgnomecanvas: remove Andreas Müller
2018-03-19 20:28 ` [PATCH 04/17] libbonoboui: remove Andreas Müller
2018-03-19 20:28 ` [PATCH 05/17] glade3: remove gnome packageconfig Andreas Müller
2018-03-19 20:29 ` [PATCH 06/17] libgnomeui: remove Andreas Müller
2018-03-19 20:29 ` [PATCH 07/17] libbonobo: remove Andreas Müller
2018-03-19 20:29 ` [PATCH 08/17] florence: remove Andreas Müller
2018-03-19 20:29 ` [PATCH 09/17] gnome-vfs: remove Andreas Müller
2018-03-19 20:29 ` [PATCH 10/17] gst-plugins-base: remove gnomevfs packageconfig Andreas Müller
2018-03-19 20:29 ` [PATCH 11/17] vlc: remove gnome-vfs packageconfig Andreas Müller
2018-03-19 20:29 ` [PATCH 12/17] libgnome: remove Andreas Müller
2018-03-19 20:29 ` [PATCH 13/17] gnome-mime-data: remove Andreas Müller
2018-03-19 20:29 ` [PATCH 14/17] gnome-themes: remove Andreas Müller
2018-03-19 20:29 ` [PATCH 15/17] orbit2: remove Andreas Müller
2018-03-19 20:29 ` [PATCH 16/17] gtk-engines: remove Andreas Müller
2018-03-19 20:29 ` [PATCH 17/17] libidl: remove Andreas Müller
2018-03-19 22:38 ` [PATCH 00/17] remove gnome2 recipes for discontinued projects Khem Raj
2018-03-20 10:18 ` Alexander Kanavin
2018-03-20 18:03   ` Andreas Müller [this message]
2018-03-22 20:47   ` Andreas Müller

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=CALbNGRStZxv6Mt3phdup6dJ-jNMHsMRNNodBJP9mSjMx62P4rg@mail.gmail.com \
    --to=schnitzeltony@gmail.com \
    --cc=alexander.kanavin@linux.intel.com \
    --cc=openembedded-devel@lists.openembedded.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.