All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] A script to clean obsolete sstate cache files
Date: Wed, 22 Feb 2012 16:43:46 +0000	[thread overview]
Message-ID: <1329929026.20261.182.camel@ted> (raw)
In-Reply-To: <CAP9ODKpro7+mBMkCismL6Ac6h8AgT6euH-hWp=cUb=Xhp4UXuQ@mail.gmail.com>

On Wed, 2012-02-22 at 14:16 -0200, Otavio Salvador wrote:
> If you look at *my* first reply to this thread I just asked him to
> resend it based on OE-Core - as he already did - so I could give it a
> test. This seemed quite friendly from my POV and he didn't complain.

You'll also notice I directed my comments to Koen's reply, not yours.

Since we're on the subject though, I do believe there is marginal value
in asking someone to rebase a single patch you could have just as easily
downloaded and applied yourself. I am respectful and protective of
people's time and in this case I think there are better ways things
could have been handled.

Overall though my main objective was to avoid these "Please rebase on
OE-Core????!!!!?" type messages and I think we've figured out a way to
do that.

> If people dislike it, it is better if they show up and don't hide behind you.

We have many different people involved with the project with different
personalities and cultural backgrounds. Open source projects should be
as open, inclusive and friendly as possible in my view. We do have some
participants who get put off by the form of some of the replies on list
and would prefer not to get involved in what could potentially become
"flame war" type discussions. I'd even personally like to avoid them to
as they kill my productivity but sadly my role means I cannot.

I am happy to listen to people's concerns and do what I can to improve
things where I see opportunities. I only received comments from one
other person about this specific thread and they have responded on list.
I have received many different comments on the general topic from
previous similar threads though so I do have an idea of some people's
feelings on this topic. I happen to have chosen this moment in time to
try and resolve the issue. I don't see an problem in any of these
things.

Cheers,

Richard




  reply	other threads:[~2012-02-22 16:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 13:27 [PATCH 0/1] A script to clean obsolete sstate cache files Robert Yang
2012-02-22 13:27 ` [PATCH 1/1] " Robert Yang
2012-02-22 13:42 ` [PATCH 0/1] " Koen Kooi
2012-02-22 14:15   ` Richard Purdie
2012-02-22 14:32     ` Koen Kooi
2012-02-22 15:06       ` Richard Purdie
2012-02-22 15:11         ` Koen Kooi
2012-02-22 16:05           ` Richard Purdie
2012-02-22 16:08             ` Otavio Salvador
2012-02-22 15:47         ` Otavio Salvador
2012-02-22 15:53           ` Paul Eggleton
2012-02-22 15:56             ` Otavio Salvador
2012-02-22 16:09               ` Richard Purdie
2012-02-22 16:16                 ` Otavio Salvador
2012-02-22 16:43                   ` Richard Purdie [this message]
2012-02-22 16:00           ` Phil Blundell
2012-02-22 14:48 ` Otavio Salvador
2012-02-24  4:13 ` Saul Wold

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=1329929026.20261.182.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --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.