From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Markus Volk <f_l_k@t-online.de>
Cc: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-gnome][PATCHv2] folks: initial add recipe
Date: Sun, 23 Jan 2022 14:51:58 +0100 [thread overview]
Message-ID: <CANNYZj_Zi+WA56H2q-woXGJkG+NJU2xUsBERSq7jua09W0dHkg@mail.gmail.com> (raw)
In-Reply-To: <58bd9ebd-583f-e7e9-6c3b-af14772c4f7e@t-online.de>
[-- Attachment #1: Type: text/plain, Size: 808 bytes --]
I added a comment there, for what it's worth.
Alex
On Sun, 23 Jan 2022 at 14:35, Markus Volk <f_l_k@t-online.de> wrote:
> What brought me to thinking this really is a design decision was this
> conversation some time back
>
> https://gitlab.gnome.org/GNOME/gimp/-/issues/7208
>
> Am 23.01.22 um 14:28 schrieb Alexander Kanavin:
> > nd see what they have to say
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#95021):
> https://lists.openembedded.org/g/openembedded-devel/message/95021
> Mute This Topic: https://lists.openembedded.org/mt/88611345/1686489
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [
> alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
[-- Attachment #2: Type: text/html, Size: 1737 bytes --]
next prev parent reply other threads:[~2022-01-23 13:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220120203602.3833757-1-f_l_k@t-online.de>
[not found] ` <33c62297-f753-3c63-d409-d6ed774ace94@t-online.de>
2022-01-22 19:54 ` [oe] [meta-gnome][PATCHv2] folks: initial add recipe Alexander Kanavin
2022-01-23 12:14 ` Markus Volk
2022-01-23 13:00 ` Alexander Kanavin
2022-01-23 13:18 ` Markus Volk
2022-01-23 13:28 ` Alexander Kanavin
2022-01-23 13:35 ` Markus Volk
2022-01-23 13:51 ` Alexander Kanavin [this message]
[not found] ` <16CCE8C3AC544122.6784@lists.openembedded.org>
2022-01-23 13:27 ` Markus Volk
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=CANNYZj_Zi+WA56H2q-woXGJkG+NJU2xUsBERSq7jua09W0dHkg@mail.gmail.com \
--to=alex.kanavin@gmail.com \
--cc=f_l_k@t-online.de \
--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.