From: andrew may <acmay@acmay•homeip.net>
To: Matt Porter <mporter@mvista•com>
Cc: Eugene Surovegin <ebs@innocent•com>,
linuxppc-embedded@lists•linuxppc.org
Subject: Re: Status of 440GP port
Date: Tue, 2 Apr 2002 13:41:09 -0800 [thread overview]
Message-ID: <20020402134109.A5189@ecam.san.rr.com> (raw)
In-Reply-To: <20020402141845.A12269@home.com>
On Tue, Apr 02, 2002 at 02:18:45PM -0700, Matt Porter wrote:
>
> On Tue, Apr 02, 2002 at 11:46:12AM -0800, Eugene Surovegin wrote:
> >
> > I checked yesterday bk://ppc.bkserver.net/linuxppc_2_4_devel tree and found
> > some preparations for this port (e.g. 4xx->40x renaming).
>
> There will be a few more preparation changes before the rest arrives.
>
> > I understand that this effort is under way for quite some time but not yet
> > released (or am I wrong?).
>
> I wouldn't say it has been underway for "quite some time". 4-5 working
> weeks is a short amount of development time for a new processor (at least
> for me). :)
So are you useing your own repository to track your development? It sure
doesn't seem like the 2_4_devel tree is a development tree anymore. And
seeing how hard it has become to get changes into the "devel" tree also
suggests that the tree is not really a development tree.
Any particular reason you are keeping things "close to your chest"? I know
it is nice to be able to go through and makes changes where ever you
like without having to be confronted with them every checkin/merge, but
since there are change that will at least change the file structure of
other boards it seems like it should be kept more in the open.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-02 21:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 19:46 Status of 440GP port Eugene Surovegin
2002-04-02 21:18 ` Matt Porter
2002-04-02 21:41 ` andrew may [this message]
2002-04-02 22:21 ` Matt Porter
2002-04-02 22:54 ` andrew may
2002-04-02 23:20 ` Matt Porter
2002-04-03 0:28 ` andrew may
2002-04-02 23:29 ` Frank Rowand
2002-04-03 0:08 ` Amit D. Chaudhary
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=20020402134109.A5189@ecam.san.rr.com \
--to=acmay@acmay$(echo .)homeip.net \
--cc=ebs@innocent$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=mporter@mvista$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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