All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Holger Hans Peter Freyther <holger+oe@freyther.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: xterm: either fix it, or remove it. please.
Date: Thu, 12 Nov 2009 02:34:37 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0911120226140.3969@localhost> (raw)
In-Reply-To: <200911120820.08344.holger+oe@freyther.de>

On Thu, 12 Nov 2009, Holger Hans Peter Freyther wrote:

> On Thursday 12 November 2009 07:36:32 Robert P. J. Day wrote:
>
> >   anyway, this is about the fourth time i've explained this,
> > either here or on the angstrom-devel list.  that's the error, and
> > it's entirely reproducible on my f11 system.  at this point, i'm
> > leaving it with the powers that be, and you're free to deal with
> > it or totally ignore it.  whatever suits you.
>
> Robert,
>
> I totally agree that bugs should be fixed. Your attitude is somehow
> weird as you demand others to fix problems you are experiencing.
> Honestly speaking I am a bit disturbed by this attitude.

  at this point, i don't much care.  recently, i've been investing
some time in OE, doing some builds and reporting bugs when i've found
them so, yes, i am *also* part of that community of which you speak.
i even promoted OE for the beagleboard when i gave a talk recently at
ontario linux fest:

  http://onlinux.ca/node/78

  when i first ran across that xterm bug, i reported it.  nothing
happened.  i waited, and mentioned it again.  eventually, philip
balister admitted that he'd reproduced it.  good, i thought, someone
else has seen it so it should be fixed eventually.

  nothing.  so i mentioned it *again*, but only after doing some
research, to the point where i tracked down the *cause* of the bug,
posted a detailed explanation of that cause, and even mentioned that
i'd verified that a proposed fix solved the problem.

  nothing.  at this point, i've quite given up on investing any more
time trying to help out.

> Work on OE is purely community driven, ...

  i'm well aware of that.  i was trying to become a productive
*member* of that community.  at this point, i've pretty much lost
interest.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================



  parent reply	other threads:[~2009-11-12  7:36 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12  5:47 xterm: either fix it, or remove it. please Robert P. J. Day
2009-11-12  5:56 ` Holger Hans Peter Freyther
2009-11-12  6:22   ` Robert P. J. Day
2009-11-12  6:22   ` Holger Hans Peter Freyther
2009-11-12  6:36     ` Robert P. J. Day
2009-11-12  7:20       ` Holger Hans Peter Freyther
2009-11-12  7:32         ` Holger Hans Peter Freyther
2009-11-12  7:34         ` Robert P. J. Day [this message]
2009-11-12  8:33           ` Michael 'Mickey' Lauer
2009-11-12  8:28         ` Graeme Gregory
2009-11-12  8:15       ` Frans Meulenbroeks
2009-11-12 12:28         ` Robert P. J. Day
2009-11-12 12:47           ` Frans Meulenbroeks
2009-11-12 12:58             ` Robert P. J. Day
2009-11-12 13:05               ` Graeme Gregory
2009-11-12 15:37                 ` Robert P. J. Day
2009-11-12 13:11               ` Holger Hans Peter Freyther
2009-11-13  8:43                 ` Robert P. J. Day
2009-11-13  8:55                 ` Robert P. J. Day
2009-11-13  9:32                   ` Graeme Gregory
2009-11-12 13:15             ` Robert P. J. Day
2009-11-12 18:49             ` Mike Westerhof
2009-11-12 21:42               ` GNUtoo
2009-11-12 21:59                 ` Philip Balister
2009-11-12 22:17                   ` Graeme Gregory
2009-11-13  4:38                   ` Robert P. J. Day
2009-11-12 11:51 ` Philip Balister

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=alpine.LFD.2.00.0911120226140.3969@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=holger+oe@freyther.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.