From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 08/11] lrzsz: remove the recipe
Date: Wed, 20 Nov 2019 22:12:25 +0100 [thread overview]
Message-ID: <CANNYZj99KZEZCHhOEQKBBguXC=mgXtb-rOAaMSX1K35ie03cSw@mail.gmail.com> (raw)
In-Reply-To: <20191120201717.GA23850@localhost>
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
On Wed, 20 Nov 2019 at 21:17, Adrian Bunk <bunk@stusta.de> wrote:
> > Do you want to maintain it?
>
> Did you already contact the maintainer whose name your patch removes
> from maintainers.inc?
>
Most entries in oe-core's maintainers.inc do not carry any real
responsibility or commitment; they're there mostly so that monthly emails
from auto upgrade helper end up with someone. Actual maintenance comes from
those who use and need the components.
I can certainly ask Anuj, but I bet he has no interest in lrzsz whatsoever.
Alex
[-- Attachment #2: Type: text/html, Size: 887 bytes --]
next prev parent reply other threads:[~2019-11-20 21:12 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 13:44 [PATCH 01/11] man-pages: correct the SRC_URI Alexander Kanavin
2019-11-20 13:44 ` [PATCH 02/11] man-pages: update to 5.03 Alexander Kanavin
2019-11-20 13:44 ` [PATCH 03/11] dummy-sdk-package.inc: do not include files into RREPLACES Alexander Kanavin
2019-11-23 14:37 ` Richard Purdie
2019-11-20 13:44 ` [PATCH 04/11] gettext-minimal-native: update to 0.20.1 Alexander Kanavin
2019-11-20 13:44 ` [PATCH 05/11] gettext: " Alexander Kanavin
2019-11-20 13:44 ` [PATCH 06/11] e2fsprogs: fix build issues with the latest version of gettext Alexander Kanavin
2019-11-20 13:44 ` [PATCH 07/11] console-tools: remove the recipe Alexander Kanavin
2019-11-20 13:44 ` [PATCH 08/11] lrzsz: " Alexander Kanavin
2019-11-20 19:49 ` Adrian Bunk
2019-11-20 20:00 ` Alexander Kanavin
2019-11-20 20:17 ` Adrian Bunk
2019-11-20 21:12 ` Alexander Kanavin [this message]
2019-11-20 21:38 ` Phil Blundell
2019-11-20 22:12 ` Alexander Kanavin
2019-11-20 22:32 ` Phil Blundell
2019-11-20 22:56 ` Alexander Kanavin
2019-11-20 23:18 ` Adrian Bunk
2019-11-21 9:24 ` Ross Burton
2019-11-21 10:10 ` Richard Purdie
2019-11-21 13:59 ` Phil Blundell
2019-11-22 0:49 ` Ross Burton
2019-11-25 12:07 ` Ross Burton
2019-11-26 11:59 ` Phil Blundell
2019-11-26 12:06 ` Phil Blundell
2019-11-26 14:49 ` Ross Burton
2019-11-27 14:32 ` Ross Burton
2019-11-27 15:07 ` Phil Blundell
2019-11-21 15:36 ` Adrian Bunk
2019-11-21 16:41 ` Richard Purdie
2019-11-20 13:44 ` [PATCH 09/11] p11-kit: convert to meson Alexander Kanavin
2019-11-23 23:04 ` Richard Purdie
2019-11-25 16:53 ` Alexander Kanavin
2019-11-20 13:44 ` [PATCH 10/11] mc: backport a patch to fix builds with latest gettext Alexander Kanavin
2019-11-20 13:44 ` [PATCH 11/11] systemtap: update to 4.2 Alexander Kanavin
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='CANNYZj99KZEZCHhOEQKBBguXC=mgXtb-rOAaMSX1K35ie03cSw@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=bunk@stusta.de \
--cc=openembedded-core@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.