From: Konstantinos Margaritis <kmargar@cc.uoa.gr>
To: linuxppc-dev@lists.linuxppc.org, linuxppc-user@lists.linuxppc.org
Subject: powerpc system open for development?
Date: Fri, 23 Apr 1999 02:05:05 +0300 [thread overview]
Message-ID: <99042302094300.00619@proton> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hi,
Is there a powerpc open system open for development? Free unix accounts of course
are required, plus many development tools. The problem is I am on a dialup system,
so some authors that I am helping in porting some programs -e.g. freeamp- cannot do
real debugging, as they cannot login and do real development. As it is debugging is
restricted to me-send-bug-report/he-sends-possible-fix/me-sends-another-bug-report/
he-sends-another-possible-fix, etc... you get the idea.
I think that something like this is necessary on an organized basis if porting
is to go any faster.
- --
Konstantinos Margaritis
kmargar@cc.uoa.gr, markos@debian.org
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
iQCVAwUBNx+sO/alfJok8qABAQFzfwP+MzOY5gcydcwbTyJhXmX0aAP9HkFd5y0K
C6H7P586VChxjybRR65Ff5J8FTrjEgXjFjLzedAKqNT8L5GDd8g5bBTPe0XB4aig
YcEu1i+8M57fm2Tr/uE82DIWAZCLQkNipRv7C81krZHDfb7wv6ZLUWEgC+IJQso9
BiZcnrAUG3s=
=Grx8
-----END PGP SIGNATURE-----
[[ 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 reply other threads:[~1999-04-22 23:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-22 23:05 Konstantinos Margaritis [this message]
1999-04-23 5:25 ` powerpc system open for development? Troy Benjegerdes
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=99042302094300.00619@proton \
--to=kmargar@cc.uoa.gr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@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).