From: David Edelsohn <dje@watson.ibm.com>
To: Tom Gall <gall@rochcivictheatre.org>
Cc: Gabriel Paubert <paubert@iram.es>,
Takashi Oe <toe@unlserve.unl.edu>,
Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
Thomas Graichen <graichen@innominate.de>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Getting things in... Was: Re: shifts on 64bit ints
Date: Fri, 04 Aug 2000 12:26:26 -0400 [thread overview]
Message-ID: <200008041626.MAA22082@mal-ach.watson.ibm.com> (raw)
In-Reply-To: Message from Tom Gall <gall@rochcivictheatre.org> of "Fri, 04 Aug 2000 11:06:36 CDT." <398AEA0C.329AB669@rochcivictheatre.org>
>>>>> Tom Gall writes:
>> linuxppc-dev is not necessarily a patch submission mailinglist.
>> Until PowerPC Linux development has such a thing, I think that it is
>> better to coordinate with and directly send patches to someone with
>> write-access who can apply the patches instead of throwing them up in the
>> air and hoping that someone catches them.
Tom> This can be a good thing or a bad thing tho. I'd rather like to see
Tom> patches posted to the list. Granted there's some line there where they
Tom> simply get too big and a link is better. At least with posting to the
Tom> list everyone has the chance to comment and better yet test them out!
I did not mean to send patches to someone *instead* of sending
them to the mailinglist. I meant that sending them to the mailinglist
solely as a way of proposing that a patch be merged into the development
tree does not make it clear what action should be taken.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-04 16:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <news-innominate.list.linux.ppc.dev@innominate.de>
2000-08-03 22:38 ` shifts on 64bit ints Thomas Graichen
2000-08-03 23:02 ` David Edelsohn
2000-08-03 23:54 ` Franz Sirl
2000-08-04 0:40 ` Takashi Oe
2000-08-04 0:50 ` Takashi Oe
2000-08-04 7:16 ` Thomas Graichen
2000-08-04 9:21 ` Gabriel Paubert
2000-08-04 15:18 ` David Edelsohn
2000-08-04 15:28 ` Kevin B. Hendricks
2000-08-04 16:06 ` Getting things in... Was: " Tom Gall
2000-08-04 16:26 ` David Edelsohn [this message]
2000-08-04 16:30 ` Tom Gall
2000-08-04 17:49 ` Benjamin Herrenschmidt
2000-08-04 18:32 ` Takashi Oe
2000-08-04 18:52 ` Hendricks, Kevin
2000-08-04 19:44 ` Takashi Oe
2000-08-04 20:10 ` Michael Schmitz
2000-08-05 5:42 ` Paul Mackerras
2000-08-05 11:51 ` Geert Uytterhoeven
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=200008041626.MAA22082@mal-ach.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=gall@rochcivictheatre.org \
--cc=graichen@innominate.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
--cc=toe@unlserve.unl.edu \
/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).