linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: platform/board removal update
Date: Tue, 26 Jul 2005 10:35:56 -0400	[thread overview]
Message-ID: <855be1bf81cc3629e58e6a23ebb50300@embeddededge.com> (raw)
In-Reply-To: <F4AA78A2-3370-406A-83B1-362250AEEC4A@freescale.com>


On Jul 26, 2005, at 9:01 AM, Kumar Gala wrote:

> All the other systems (apus, gemini, rpxcllf) were more effort than I 
> was wanting to deal with.

Why?  The rpxcllf worked not long ago.  What happened to the courtesy of
the past when such updates were applied to all platforms such they
would at least build?  After such changes, if there is still a problem, 
the
person should at least contact the maintainer to get it resolved.  I 
don't
appreciate being demanded to fix something within a short period of
time that someone else broke or else everything I've done in the past
will be discarded.

Thanks.


	-- Dan

  reply	other threads:[~2005-07-26 14:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26  4:18 platform/board removal update Kumar Gala
2005-07-26 13:01 ` Kumar Gala
2005-07-26 14:35   ` Dan Malek [this message]
2005-07-26 14:43     ` Kumar Gala
2005-07-26 10:05       ` Marcelo Tosatti
2005-07-26 22:14         ` Dan Malek
2005-07-26 10:34           ` Marcelo Tosatti
2005-07-27 21:46         ` 'Aristeu Sergio Rozanski Filho'
2005-07-28  6:29           ` Pantelis Antoniou
2005-07-28 13:03             ` 'Aristeu Sergio Rozanski Filho'

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=855be1bf81cc3629e58e6a23ebb50300@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).