public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "C C" <daiso1789@gmail.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: WELCOME to gcc@gcc.gnu.org
Date: Mon, 30 Jul 2007 00:10:00 -0000	[thread overview]
Message-ID: <3ac34dc00707291710h23824894pfae1561d82ddacea@mail.gmail.com> (raw)
In-Reply-To: <1185754212.17343.ezmlm@gcc.gnu.org>

On 30 Jul 2007 00:10:12 -0000, gcc-help@gcc.gnu.org
<gcc-help@gcc.gnu.org> wrote:
> Hi! This is the ezmlm program. I'm managing the
> gcc@gcc.gnu.org mailing list.
>
> Acknowledgment: I have added the address
>
>   daiso1789@gmail.com
>
> to the gcc mailing list.
>
> Welcome to gcc@gcc.gnu.org!
>
> Please save this message so that you know the address you are
> subscribed under, in case you later want to unsubscribe or change your
> subscription address.
>
>
> --- Administrative commands for the gcc list ---
>
> I can handle administrative requests automatically. Please
> do not send them to the list address! Instead, send
> your message to the correct command address:
>
> To subscribe to the list, send a message to:
>   <gcc-subscribe@gcc.gnu.org>
>
> To remove your address from the list, send a message to:
>   <gcc-unsubscribe@gcc.gnu.org>
>
> Send mail to the following for info and FAQ for this list:
>   <gcc-info@gcc.gnu.org>
>   <gcc-faq@gcc.gnu.org>
>
> Similar addresses exist for the digest list:
>   <gcc-digest-subscribe@gcc.gnu.org>
>   <gcc-digest-unsubscribe@gcc.gnu.org>
>
> To get messages 123 through 145 (a maximum of 100 per request), mail:
>   <gcc-get.123_145@gcc.gnu.org>
>
> To get an index with subject and author for messages 123-456 , mail:
>   <gcc-index.123_456@gcc.gnu.org>
>
> They are always returned as sets of 100, max 2000 per request,
> so you'll actually get 100-499.
>
> To receive all messages with the same subject as message 12345,
> send an empty message to:
>   <gcc-thread.12345@gcc.gnu.org>
>
> The messages do not really need to be empty, but I will ignore
> their content. Only the ADDRESS you send to is important.
>
> You can start a subscription for an alternate address,
> for example "john@host.domain", just add a hyphen and your
> address (with '=' instead of '@') after the command word:
> <gcc-subscribe-john=host.domain@gcc.gnu.org>
>
> To stop subscription for this address, mail:
> <gcc-unsubscribe-john=host.domain@gcc.gnu.org>
>
> In both cases, I'll send a confirmation message to that address. When
> you receive it, simply reply to it to complete your subscription.
>
> If despite following these instructions, you do not get the
> desired results, please contact my owner at
> gcc-owner@gcc.gnu.org. Please be patient, my owner is a
> lot slower than I am ;-)
>
> --- Enclosed is a copy of the request I received.
>
> Return-Path: <daiso1789@gmail.com>
> Received: (qmail 17338 invoked by uid 22791); 30 Jul 2007 00:10:12 -0000
> X-Spam-Status: No, hits=-1.9 required=5.0
>        tests=BAYES_00,DK_POLICY_SIGNSOME,DK_SIGNED,SARE_MSGID_LONG40,SPF_PASS,TW_ZM
> X-Spam-Check-By: sourceware.org
> Received: from ug-out-1314.google.com (HELO ug-out-1314.google.com) (66.249.92.170)
>    by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 30 Jul 2007 00:10:09 +0000
> Received: by ug-out-1314.google.com with SMTP id m2so1102412ugc
>        for <gcc-sc.1185754176.bhdabhamanfgldebfjad-daiso1789=gmail.com@gcc.gnu.org>; Sun, 29 Jul 2007 17:10:06 -0700 (PDT)
> DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;
>        d=gmail.com; s=beta;
>        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
>        b=dmbjq92rLJ4J1B2C4X8i2BYQ0i1B7IRe4qI2oi2acMG2K/D/bojbw5ACEVzKX2x1jJcul+E7Y7xNJBrqQF0zhyVd8FtBpbdrCIE4rulEAkItbo0l4Ir9dWBlXYqrFOUTCB8ASHAfXcZf57JvX3Krx+l8+/5VqBUOX0ivy8sj0L4=
> DomainKey-Signature: a=rsa-sha1; c=nofws;
>        d=gmail.com; s=beta;
>        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
>        b=X4YmC3qISq8xv+e+HCGYUoi4ZiNvKaf/kEuYcKjukgiF5jDay+byCoNrExiiIR2lUul/NKg+TJAnE72oRVu3vMqvrvH1gzy9m/mxlXtjbMJ/DVEK1U/CCxax/aOY1jqcVT6J5gqZVheCVOJAqomtTWD7HtTy92d7V0U7gGIWuyI=
> Received: by 10.78.136.9 with SMTP id j9mr1332141hud.1185754206467;
>        Sun, 29 Jul 2007 17:10:06 -0700 (PDT)
> Received: by 10.78.140.2 with HTTP; Sun, 29 Jul 2007 17:10:06 -0700 (PDT)
> Message-ID: <3ac34dc00707291710v323da20bnc960ca12ccc2126d@mail.gmail.com>
> Date: Sun, 29 Jul 2007 21:10:06 -0300
> From: "C C" <daiso1789@gmail.com>
> To: gcc-sc.1185754176.bhdabhamanfgldebfjad-daiso1789=gmail.com@gcc.gnu.org
> Subject: Re: confirm subscribe to gcc@gcc.gnu.org
> In-Reply-To: <1185754176.17041.ezmlm@gcc.gnu.org>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> References: <1185754176.17041.ezmlm@gcc.gnu.org>
>
> On 30 Jul 2007 00:09:36 -0000, gcc-help@gcc.gnu.org
> <gcc-help@gcc.gnu.org> wrote:
> > Hi! This is the ezmlm program. I'm managing the
> > gcc@gcc.gnu.org mailing list.
> >
> > To confirm that you would like
> >
> >   daiso1789@gmail.com
> >
> > added to the gcc mailing list, please send
> > an empty reply to this address:
> >
> >   gcc-sc.1185754176.bhdabhamanfgldebfjad-daiso1789=gmail.com@gcc.gnu.org
> >
> > Usually, this happens when you just hit the "reply" button.
> > If this does not work, simply copy the address and paste it into
> > the "To:" field of a new message.
> >
> > This confirmation serves two purposes. First, it verifies that I am able
> > to get mail through to you. Second, it protects you in case someone
> > forges a subscription request in your name.
> >
> > Some mail programs are broken and cannot handle long addresses. If you
> > cannot reply to this request, instead send a message to
> > <gcc-request@gcc.gnu.org> and put the
> > entire address listed above into the "Subject:" line.
> >
> >
> > --- Administrative commands for the gcc list ---
> >
> > I can handle administrative requests automatically. Please
> > do not send them to the list address! Instead, send
> > your message to the correct command address:
> >
> > To subscribe to the list, send a message to:
> >   <gcc-subscribe@gcc.gnu.org>
> >
> > To remove your address from the list, send a message to:
> >   <gcc-unsubscribe@gcc.gnu.org>
> >
> > Send mail to the following for info and FAQ for this list:
> >   <gcc-info@gcc.gnu.org>
> >   <gcc-faq@gcc.gnu.org>
> >
> > Similar addresses exist for the digest list:
> >   <gcc-digest-subscribe@gcc.gnu.org>
> >   <gcc-digest-unsubscribe@gcc.gnu.org>
> >
> > To get messages 123 through 145 (a maximum of 100 per request), mail:
> >   <gcc-get.123_145@gcc.gnu.org>
> >
> > To get an index with subject and author for messages 123-456 , mail:
> >   <gcc-index.123_456@gcc.gnu.org>
> >
> > They are always returned as sets of 100, max 2000 per request,
> > so you'll actually get 100-499.
> >
> > To receive all messages with the same subject as message 12345,
> > send an empty message to:
> >   <gcc-thread.12345@gcc.gnu.org>
> >
> > The messages do not really need to be empty, but I will ignore
> > their content. Only the ADDRESS you send to is important.
> >
> > You can start a subscription for an alternate address,
> > for example "john@host.domain", just add a hyphen and your
> > address (with '=' instead of '@') after the command word:
> > <gcc-subscribe-john=host.domain@gcc.gnu.org>
> >
> > To stop subscription for this address, mail:
> > <gcc-unsubscribe-john=host.domain@gcc.gnu.org>
> >
> > In both cases, I'll send a confirmation message to that address. When
> > you receive it, simply reply to it to complete your subscription.
> >
> > If despite following these instructions, you do not get the
> > desired results, please contact my owner at
> > gcc-owner@gcc.gnu.org. Please be patient, my owner is a
> > lot slower than I am ;-)
> >
> > --- Enclosed is a copy of the request I received.
> >
> > Return-Path: <anonymous@gcc.gnu.org>
> > Received: (qmail 17036 invoked by uid 48); 30 Jul 2007 00:09:36 -0000
> > Date: 30 Jul 2007 00:09:36 -0000
> > Message-ID: <20070730000936.17035.qmail@sourceware.org>
> > From: anonymous@gcc.gnu.org
> > To: gcc-subscribe-daiso1789=gmail.com@gcc.gnu.org
> >
> >
> >
>

       reply	other threads:[~2007-07-30  0:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1185754212.17343.ezmlm@gcc.gnu.org>
2007-07-30  0:10 ` C C [this message]
     [not found] <1209989415.7808.ezmlm@gcc.gnu.org>
2008-05-05 12:12 ` Bobby McNulty
2004-09-09 23:57 Ramadass, Ramanathan
     [not found] <1094766964.6502.ezmlm@gcc.gnu.org>
2004-09-09 21:58 ` Amit Rai
     [not found] <1081386777731314374.0.ppp14@ppp14>
2004-04-08  1:22 ` Hoe-Seong Ha
     [not found] <1069173774.4662.ezmlm@gcc.gnu.org>
2003-11-25 14:39 ` Bharat Madan
2003-11-25 17:16   ` Claudio Bley
     [not found] <1046975368.30972.ezmlm@gcc.gnu.org>
2003-03-09 13:28 ` monika chaddha
  -- strict thread matches above, loose matches on Subject: below --
2003-02-26 14:23 Rakesh Kumar, Noida
     [not found] <1025975583.2777.ezmlm@gcc.gnu.org>
2002-07-08  6:18 ` Steve
2002-03-26  2:04 Sathis Kanna
2000-06-29 22:00 pearce_sm
2000-06-20 15:10 dante666

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=3ac34dc00707291710h23824894pfae1561d82ddacea@mail.gmail.com \
    --to=daiso1789@gmail.com \
    --cc=gcc-help@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).