From: Wolfgang Denk <wd@denx.de>
To: linuxppc-dev@lists.linuxppc.org
Cc: jpeters@phx.mcd.mot.com
Subject: Re: Motorola Web Site
Date: Wed, 28 Jul 1999 15:36:13 +0200 [thread overview]
Message-ID: <199907281336.PAA20067@denx.muc.de> (raw)
In-Reply-To: Your message of "Wed, 28 Jul 1999 09:54:03 +0200." <m119OXL-0000WZC@tri-yann.crf.canon.fr>
In message <m119OXL-0000WZC@tri-yann.crf.canon.fr> you write:
>
> While it is nce to have motorola *effectively* supporting linux
Yes - thanks, Motorola!
> may I make the follwoing comments :
>
> 1) The form you need to fill to access patches is quite
> painfull and if the purpose is only to notify users of
> patch changes, then email would be sufficient...
Agreed. I do not like at all being forced to supply such information
if I want or not. Please remove this!
You may add a link where anybody who *wants* notifications of changed
*may* register, but please do not try to force us!
An additional disadvantage of the current interface is that it
disallows for automatic downloads using wget or similar tools.
> 2) The patch for 2.2.10 is 1.5 MB. It could have been
> compressed!!!
;-)
3) Is Motorola going to extend it's Linux support to the embedded controllers
(MPC8xx, MPX82xx) ?
4) Running a diff against the original 2.2.10 distribution results in
*all* files being different; why were all the $Id$ strings
changed?
For instance - I guess there were not so many changes for the
Alpha prom code:
-> diff linux-2.2.10/arch/mips/sgi/prom/misc.c linux_mot/arch/mips/sgi/prom/misc.c
1c1
< /* $Id: misc.c,v 1.6 1998/07/08 15:59:13 ralf Exp $
---
> /* $Id: misc.c,v 1.3 1998/11/10 02:14:56 jpeters Exp $
This makes it basicly impossible to find out what *really* was
changed.
Wolfgang
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: -88 Home: -86 Email: wd@denx.muc.de
"Summit meetings tend to be like panda matings. The expectations are
always high, and the results usually disappointing." - Robert Orben
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-07-28 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-27 22:05 Motorola Web Site Johnnie Peters
1999-07-27 21:25 ` Tim Waugh
1999-07-28 7:54 ` VALETTE Eric
1999-07-28 13:36 ` Wolfgang Denk [this message]
1999-07-28 20:05 ` Matt Porter
1999-08-06 21:20 ` Dave Wolfe
1999-07-29 14:03 ` Alan Cox
1999-07-29 14:03 ` Alan Cox
[not found] <4575832C8E71D111AC4100A0C96B512704A633F5@fmsmsx36.fm.intel.com>
1999-07-27 23:33 ` Johnnie Peters
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=199907281336.PAA20067@denx.muc.de \
--to=wd@denx.de \
--cc=jpeters@phx.mcd.mot.com \
--cc=linuxppc-dev@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).