linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
To: David Edelsohn <dje@watson.ibm.com>
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: shifts on 64bit ints
Date: Fri, 04 Aug 2000 11:28:42 -0400	[thread overview]
Message-ID: <398AE12A.523F3CFE@ivey.uwo.ca> (raw)
In-Reply-To: 200008041518.LAA25218@mal-ach.watson.ibm.com


Hi,

But if they are not cc'd to the linuxppc-dev list then we do need some sort of
CHANGELOG process going on.  None of the rsync trees seem to do any versioning.

Possibly we should have our own kernel mailing lists for patches and things.

Kevin

David Edelsohn wrote:
>
> >>>>> Gabriel Paubert writes:
>
> Gabriel> I plan to send a lot of small obvious bugfixes in the next 3-4 weeks, the
> Gabriel> diffs between  my tree and the official one now run in the megabyte range,
> Gabriel> and this is too much (would the BitKeeper tree accept the VME patches and
> Gabriel> PrePboot BTW ?)
>
> Gabriel> What I would for one like to see is that people that write a patch that
> Gabriel> may affect other machines than their own first publish it on this list and
> Gabriel> wait a couple of days for comment and test results before pushing it to
> Gabriel> the official source tree, somewhat like what happens on gcc-patches.
>
>         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.
>
> David
>

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

  reply	other threads:[~2000-08-04 15:28 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 [this message]
2000-08-04 16:06             ` Getting things in... Was: " Tom Gall
2000-08-04 16:26               ` David Edelsohn
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=398AE12A.523F3CFE@ivey.uwo.ca \
    --to=khendricks@ivey.uwo.ca \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=dje@watson.ibm.com \
    --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).