From: JBRUCHON <jbruchon@nc.rr.com>
To: linux-8086@vger.kernel.org
Subject: Re: New user wanting to help
Date: Sun, 18 Nov 2007 17:11:16 -0500 [thread overview]
Message-ID: <4740B884.8070200@nc.rr.com> (raw)
In-Reply-To: <33315.1756.qm@web50504.mail.re2.yahoo.com>
I'm sort of the current maintainer of the site and the project, but have no
access to the mailing list setup at all.
I'm a fairly busy person so I don't do much without being asked to do it,
and my web-fu sucks pretty bad.
If you want something in particular done, give me the resources and I'll get
it done.
Ben Weiss wrote:
> --- Hans <hans64@ht-lab.com> wrote:
>
>> I am a bit disappointed that Rask Lambertsen's GCC
>> port and the Dioscuri
>> emulator (which runs ELKS!) are not mentioned on the
>> website, come on guys,
>> it can't be that much work to add some hyperlinks...
>
> This seems like the easiest thing to fix first, and
> makes the project "look" better, so I'd be happy to
> provide some updates to the site. Not too much for
> now, just keeping with static pages- fixing broken
> links, adding some (ie Rasks's port), etc. Does anyone
> know who needs to be contacted to update the archive
> mentioned on vger.kernel.org? Is this list still even
> being archived, or do we have to "sign up" for it? (If
> so, gmane comes to mind...)
>
>> Compiling ELKS under GCC is not going to be
>> easy but IMHO will be very
>> beneficial for the wider embedded user community and
>> hence will/might
>> increase the popularity of ELKS.
>
> Sounds like great minds think alike :)
> Not only is GCC much more popular and continuously
> maintained, but apparently GCC (GAS, rather) uses AT&T
> syntax, and BCC uses Intel syntax. Since Linux uses
> GCC, it follows that modifying/porting to ELKS would
> be easier if we also use GCC.
>
> -Ben
>
>
> ____________________________________________________________________________________
> Get easy, one-click access to your favorites.
> Make Yahoo! your homepage.
> http://www.yahoo.com/r/hs
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2007-11-18 22:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 3:46 New user wanting to help Ben Weiss
2007-11-17 11:14 ` Hans
2007-11-17 16:18 ` Sebastian Rosenkiewicz
2007-11-18 22:01 ` Ben Weiss
2007-11-18 22:11 ` JBRUCHON [this message]
2007-11-19 9:35 ` Hans
2007-11-19 14:25 ` JBRUCHON
2007-11-19 14:52 ` Mario Frasca
2007-11-19 14:56 ` JBRUCHON
2007-11-19 15:04 ` Mario Frasca
2007-11-19 15:15 ` Mario Frasca
2007-11-19 15:22 ` JBRUCHON
2007-11-19 15:34 ` Hans
2007-11-19 15:44 ` Mario Frasca
2007-11-19 15:56 ` Hans
2007-11-19 15:53 ` JBRUCHON
2007-11-18 23:02 ` Mario Frasca
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=4740B884.8070200@nc.rr.com \
--to=jbruchon@nc.rr.com \
--cc=linux-8086@vger.kernel.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