Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 08/11] lrzsz: remove the recipe
Date: Thu, 21 Nov 2019 01:18:12 +0200	[thread overview]
Message-ID: <20191120231812.GB3962@localhost> (raw)
In-Reply-To: <CANNYZj93tJxTsCwS3cg3J=0WB--A0Af26Y=nO9fOdfNb9okRYg@mail.gmail.com>

On Wed, Nov 20, 2019 at 11:56:38PM +0100, Alexander Kanavin wrote:
> On Wed, 20 Nov 2019 at 23:32, Phil Blundell <pb@pbcl.net> wrote:
> 
> > However, I think the point still stands that the commit message needs to
> > provide a better description of why the package is being removed.  If you
> > think it represents an ongoing maintenance headache that's already bad and
> > only going to get worse, and this now outweighs its usefulness, let's just
> > say that.  Not all old software is problematic, and not all problematic
> > software is old; the fact that the last release was 20 years ago is an
> > interesting fact but in isolation that doesn't represent a problem.
> > Indeed, compared to some other packages in oe-core, eight patches in
> > total over a 20-year period doesn't seem like that bad of an average.
> >
> 
> Fair enough, I wrote a hasty commit message. Mistakes happen.
> 
> Can I say what my problem is? Here goes: so far, no one in this discussion
> offered actual help with the actual issue. If you need this or that
> functionality from Yocto, please try to place help ahead of complaints and
> criticism.

No, your problem is your way of communication.

It is a very unfriendly way of communication to request help in the form 
patch aiming at immediate removal.

It comes across as if you were just too lazy to even try to fix 
something another patch you are submitting is breaking.

You would have received more constructive answers if you would have 
started with an email describing the non-trivial technical problem
where you need assistance.

> Alex

cu
Adrian


  reply	other threads:[~2019-11-20 23:18 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
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 [this message]
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=20191120231812.GB3962@localhost \
    --to=bunk@stusta.de \
    --cc=alex.kanavin@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox