From: Keith Marshall <keithmarshall@users.sourceforge.net>
To: MinGW Users List <mingw-users@lists.sourceforge.net>
Cc: Me Myself and I <stargate7thsymbol@live.co.uk>, java@gcc.gnu.org
Subject: Re: [Mingw-users] Question about GNU Compiler for Java email list.
Date: Wed, 06 Apr 2011 06:55:00 -0000 [thread overview]
Message-ID: <4D9C0E34.8070205@users.sourceforge.net> (raw)
In-Reply-To: <BAY159-w15957492D1D8B714D6F0E0D0A50@phx.gbl>
On 06/04/11 01:17, Me Myself and I wrote:
>
> What is the present, working email list that I can send my MINGW32, GCJ
> email questions to?
This is it.
> Where/how may I be subscribed?
You already are subscribed. Your previous posts have been rejected
because they have been way too big. Don't post with megabyte sized
attachments; the limit is 140kB.
--
Regards,
Keith.
parent reply other threads:[~2011-04-06 6:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <BAY159-w15957492D1D8B714D6F0E0D0A50@phx.gbl>]
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=4D9C0E34.8070205@users.sourceforge.net \
--to=keithmarshall@users.sourceforge.net \
--cc=java@gcc.gnu.org \
--cc=mingw-users@lists.sourceforge.net \
--cc=stargate7thsymbol@live.co.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).