linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: acmay@acmay.homeip.net
To: jpeters@mvista.com
Cc: andrew may <acmay@acmay.homeip.net>,
	John Tyner <jtyner@cs.ucr.edu>,
	linuxppc-commit@source.mvista.com,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: ppc405 enet changes (fwd)
Date: Wed, 5 Sep 2001 09:09:53 -0700	[thread overview]
Message-ID: <20010905090953.B621@sink.san.rr.com> (raw)
In-Reply-To: <3B9632EB.51904875@mvista.com>; from jpeters@mvista.com on Wed, Sep 05, 2001 at 07:12:59AM -0700


On Wed, Sep 05, 2001 at 07:12:59AM -0700, jpeters@mvista.com wrote:
....
> It is probably time for some more clean up in it.  Remember that the
> people who are responding to you have been working at this level
> for a long time.  They have the say (or at least some of it) because
> they have shown they know what they are doing.  It you get
> defensive and make statements like you did below you will drive
> people away.

You have noticed that you are defending yourself. You should also
notice that having to send a lot of emails to get a patch in would have
tendency to prevent people from even bothering to send patches.

The focus should be on the code, listing your work history is
not a good defense of the code that is there.

We can include a "Thank You for getting things working in bad
conditions" with the patch if it makes it go in any smoother.

If you read the lkml for any amount of time you will notice
that resends, follow-ups, insults, and bruised egos are all
part of the game of getting a patch in.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2001-09-05 16:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.30.0109031513110.21186-200000@hill.cs.ucr.edu>
     [not found] ` <20010903202915.A25163@cpe-24-221-152-185.az.sprintbbd.net>
2001-09-04 20:07   ` ppc405 enet changes (fwd) andrew may
     [not found] ` <3B9557CA.D76C70E2@mvista.com>
2001-09-04 22:26   ` andrew may
2001-09-05  0:06     ` Dan Malek
     [not found]       ` <20010904180915.E14548@ecam.san.rr.com>
2001-09-05  2:39         ` Tom Rini
     [not found]     ` <3B9632EB.51904875@mvista.com>
2001-09-05 16:09       ` acmay [this message]
2001-09-05 16:25       ` acmay

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=20010905090953.B621@sink.san.rr.com \
    --to=acmay@acmay.homeip.net \
    --cc=jpeters@mvista.com \
    --cc=jtyner@cs.ucr.edu \
    --cc=linuxppc-commit@source.mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).