From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings
Date: Tue, 12 Aug 2014 05:29:38 +0000 (UTC) [thread overview]
Message-ID: <pan$505e0$4d6673ef$5d6215c4$40d095da@cox.net> (raw)
In-Reply-To: CAB7-uLmwQUxMEerb1omMmN4SE9my7mwOa=LCRK_Wf3Dak9mX9g@mail.gmail.com
[Mailed direct and to list.]
Tyler Pohl posted on Mon, 11 Aug 2014 21:20:17 -0700 as excerpted:
> how to i get off these mailing lists?
Follow the instructions, as found in the headers of every mail on the
list including the one you replied to, or the ones on the site you
presumably signed up from? Seriously:
Headers:
> List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
> List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
> List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
> List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
Page at http://www.gentoo.org/main/en/lists.xml, clearly linked via the
lists link on the gentoo homepage:
<quote>
To unsubscribe from a list, send an empty email to:
listname+unsubscribe@lists.gentoo.org
Note: You must use the identical address that you subscribed with to
unsubscribe successfully. If your email address is now forwarded/
rewritten beyond your control, please contact the list owner via listname
+owner@lists.gentoo.org with a request for manual removal.
You will then recieve a unsubscription confirmation request (double opt-
in) from the list manager, that you must reply to if you wish to be
unsubscribed.
</quote>
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-08-12 5:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 12:22 [gentoo-dev] gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings Sergei Trofimovich
2014-08-11 20:34 ` Bertrand Jacquin
2014-08-12 18:32 ` Michał Górny
2014-08-12 1:48 ` William Hubbs
2014-08-12 1:59 ` Manuel Rüger
2014-08-12 2:42 ` William Hubbs
2014-08-12 4:20 ` Tyler Pohl
2014-08-12 5:29 ` Duncan [this message]
2014-08-12 11:33 ` [gentoo-dev] " Alex Xu
2014-08-12 12:47 ` [gentoo-dev] " hasufell
2014-08-12 13:26 ` Rich Freeman
2014-08-12 14:26 ` hasufell
2014-08-12 16:24 ` William Hubbs
2014-08-12 18:37 ` Chris Reffett
2014-08-12 21:08 ` hasufell
2014-08-12 13:54 ` Ian Stakenvicius
2014-08-12 14:04 ` [gentoo-dev] repoman --nonag (was Re: gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings ) Ian Stakenvicius
2014-08-12 16:36 ` Rich Freeman
2014-08-12 16:57 ` Ian Stakenvicius
2014-08-12 17:08 ` hasufell
2014-08-12 17:13 ` Ian Stakenvicius
2014-08-12 17:25 ` Rich Freeman
2014-08-12 17:46 ` William Hubbs
2014-08-12 19:01 ` Michał Górny
2014-08-12 19:11 ` Ian Stakenvicius
2014-08-13 8:47 ` Tom Wijsman
2014-08-12 18:46 ` [gentoo-dev] gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings Michał Górny
2014-08-18 14:10 ` Ben de Groot
2014-08-13 8:38 ` Tom Wijsman
2014-08-13 16:36 ` [gentoo-dev] " Duncan
2014-08-12 22:00 ` [gentoo-dev] " Alexander Berntsen
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='pan$505e0$4d6673ef$5d6215c4$40d095da@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.gentoo.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