From: "Zack Weinberg" <zack@codesourcery.com>
To: overseers <overseers@sources.redhat.com>
Subject: [(nowhere)] [¼ö½Å°ÅºÎ] Re: GCC Mainline is in Stage 3
Date: Fri, 17 Oct 2003 17:31:00 -0000 [thread overview]
Message-ID: <87u167wz2r.fsf@egil.codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
I get one of these bounces for every message I send to gcc@.
I ran the Korean text below through a machine translator and got
| Subject: [ Reception refusal ] Re: GCC Mainline is in Stage 3
|
| The addressee from the zack@codesourcery.com it refused the reception
| of the mail which comes.
|
| Korea and America lu mail (http://mail.hanmir.com/
|
| Our meal li the internet agitation point Korea and America which leads
| lu (the http://www.hanmir.com/)
This smells like someone who doesn't know how to unsubscribe.
Would one of you be so kind as to take them off the list?
zw
[-- Attachment #2: Type: message/rfc822, Size: 3925 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 322 bytes --]
^[,A<v=E@Z0!^[(B zack@codesourcery.com ^[,A7N:NEM^[(B ^[,A?@4B^[(B ^[,A8^@O@G^[(B ^[,A<v=E@;^[(B ^[,A0E:NGO?4=@4O4Y^[(B.
_________________________________________________________
^[,AGQ9L8#^[(B ^[,A8^@O^[(B ( http://mail.hanmir.com/ )
^[,A?l8.3"8.^[(B ^[,AEkGO4B^[(B ^[,A@NEM3]^[(B ^[,A>FAvF.^[(B ^[,AGQ9L8#^[(B ( http://www.hanmir.com/ )
[-- Attachment #2.1.2: Type: message/rfc822, Size: 2153 bytes --]
Received: from 127.0.0.1 (127.0.0.1)
at KTMAIL with ESMTP Hanmir
by hitel.net;Sat, 18 Oct 2003 01:44:55 +0900
X-MsgID: 1066409095971674536.18.hitel
Message-ID: <1066409095971674536.18.hitel@hitel.net>
X-RECEIVED-IP: 67.72.78.213
Received: (qmail 26894 invoked by alias); 17 Oct 2003 16:44:24 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:gcc-unsubscribe-hydool=hitel.net@gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Delivered-To: mailing list gcc@gcc.gnu.org
Received: (qmail 26886 invoked from network); 17 Oct 2003 16:44:23 -0000
Received: from unknown (HELO mail.codesourcery.com) (65.73.237.138)
by sources.redhat.com with SMTP; 17 Oct 2003 16:44:23 -0000
Received: (qmail 2564 invoked from network); 17 Oct 2003 16:42:00 -0000
Received: from taltos.codesourcery.com (zack@66.92.218.83)
by mail.codesourcery.com with DES-CBC3-SHA encrypted SMTP; 17 Oct 2003
16:42:00 -0000
Received: by taltos.codesourcery.com (sSMTP sendmail emulation); Fri, 17 Oct
2003 09:44:22 -0700
From: "Zack Weinberg" <zack@codesourcery.com>
To: mark@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: GCC Mainline is in Stage 3
References: <1066405387.25550.25.camel@doubledemon.codesourcery.com>
Date: Fri, 17 Oct 2003 09:44:22 -0700
In-Reply-To: <1066405387.25550.25.camel@doubledemon.codesourcery.com> (Mark
Mitchell's message of "Fri, 17 Oct 2003 08:43:07 -0700")
Y-Message-ID: <871xtbyftl.fsf@egil.codesourcery.com>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-length: 470
Mark Mitchell <mark@codesourcery.com> writes:
> The GCC mainline is now in Stage 3.
>
> Stage 3 is our final stage before branching for a release. No new
> functionality should be introduced during this stage; only bug-fixes for
> existing functionality should be added and approved.
There are a lot of patches for functionality that are floating around,
having been submitted well before the deadline, but which have not yet
been reviewed. Are these excluded?
zw
From: "Zack Weinberg" <zack@codesourcery.com>
To: mark@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: GCC Mainline is in Stage 3
Date: Fri, 17 Oct 2003 09:44:22 -0700
Message-ID: <1066409095971674536.18.hitel@hitel.net>
Mark Mitchell <mark@codesourcery.com> writes:
> The GCC mainline is now in Stage 3.
>
> Stage 3 is our final stage before branching for a release. No new
> functionality should be introduced during this stage; only bug-fixes for
> existing functionality should be added and approved.
There are a lot of patches for functionality that are floating around,
having been submitted well before the deadline, but which have not yet
been reviewed. Are these excluded?
zw
next reply other threads:[~2003-10-17 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 17:31 Zack Weinberg [this message]
2003-10-17 22:03 ` Ian Lance Taylor
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=87u167wz2r.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=overseers@sources.redhat.com \
/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).