All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] move to opkg
Date: Sun, 23 Mar 2008 08:25:41 -0500	[thread overview]
Message-ID: <47E65A55.6010107@dls.net> (raw)
In-Reply-To: <fs5dbl$n1g$1@ger.gmane.org>

Koen Kooi wrote:
...
> I believe these sorts of problems stem from the fact that you don't have
> the time to keep up with the pace of .dev, 

Bullshit.  You sent the RFC on Tuesday, with ZERO documentation on the 
impact.  See the email chain -- you were practically evasive on the 
impact to distro maintainers.  You them made the change on before even a 
week had gone by, a holiday weekend at that.  Actually it was closer to 
4 days (total) and no documentation at all for anyone to assess the impact.

No, the problem is that YOU didn't take the time to wait before you 
jammed a totally undocumented and insufficently-understood 
highly-invasive change onto the entire community!

so I really think distros
> like unslung are better of using the stable branch, instead of wasting
> energy trying to keep up with .dev.
You just jumped to a conclusion.  Unslung was mentioned ONCE.  This is 
the SlugOS distro - I haven't even gotten to try to untangle Unslung yet.

And no, this change was not yet ready for .dev -- this should have been 
on a branch where it could have been tested against other distros. 
Don't shove your pushing of an unfinished bit of work onto anyone else 
as their fault.

> That being said, I don't think OE developers sit at their desks trying
> to thinks how to make life difficult for distro maintainer.

Nope.  I don't think that either.  I think that merely one particular 
change got pushed because one particular developer decided it was too 
difficult for him to document more thoroughly and was too impatient to 
wait for more feedback.

> Koen

Now, how about a helpful email?  You sent your email accusing me of 
being to lazy and unable to keep up with .dev.  I've responded in kind 
with my email.  Koen, how about solving a problem instead of just trying 
to blame me?

Mike (mwester)



  reply	other threads:[~2008-03-23 13:25 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18  8:55 [RFC] move to opkg Koen Kooi
2008-03-18  9:55 ` Junqian Gordon Xu
2008-03-19 15:33   ` WPkg Silvano Catinella
2008-03-25 17:23     ` WPkg Michael 'Mickey' Lauer
2008-03-25 23:42       ` WPkg Rod Whitby
2008-04-01  9:15         ` WPkg Silvano Catinella
2008-03-18  9:56 ` [RFC] move to opkg Marcin Juszkiewicz
2008-03-18 10:09   ` Koen Kooi
2008-03-18 10:42     ` Koen Kooi
2008-03-18 11:34       ` Jacob Thebault-Spieker
2008-03-18 11:42 ` Koen Kooi
2008-03-18 13:49 ` Geoffrey Wossum
2008-03-18 14:32   ` Koen Kooi
2008-03-18 16:48     ` Richard Purdie
2008-03-18 17:05       ` Koen Kooi
2008-03-23  0:38         ` Mike (mwester)
2008-03-23  5:17           ` Mike (mwester)
2008-03-23 10:43             ` Marcin Juszkiewicz
2008-03-23 11:02             ` Koen Kooi
2008-03-23 13:25               ` Mike (mwester) [this message]
2008-03-23 18:18               ` Tom Rini
2008-03-23 18:55                 ` Koen Kooi
2008-03-23 22:20                   ` Tom Rini
2008-03-23 23:10                     ` Rod Whitby
2008-03-23 23:06           ` Richard Purdie
2008-03-23 23:46             ` Rod Whitby
2008-03-24  4:30             ` Mike (mwester)
2008-03-24  7:55               ` Stelios Koroneos
2008-03-18 18:12     ` Tom Rini
2008-03-18 18:18       ` Mikhail Gusarov
2008-03-18 18:40         ` Koen Kooi
2008-03-19  9:06           ` Richard Purdie
2008-03-19  9:13             ` Marcin Juszkiewicz
2008-03-18 14:35   ` Marcin Juszkiewicz
2008-03-18 22:00 ` Koen Kooi
2008-03-19 17:52 ` [RFC] move to opkg / md5 error on big-endian machine Jeremy Lainé
2008-03-22 20:38   ` Jeremy Lainé
2008-03-23 10:59 ` [RFC] move to opkg Jeremy Lainé

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=47E65A55.6010107@dls.net \
    --to=mwester@dls.net \
    --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.