From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: zsh-workers@zsh.org
Subject: Re: gmane and gmane.comp.shells.zsh.devel
Date: Thu, 4 Jun 2015 12:01:58 +0100 [thread overview]
Message-ID: <20150604110158.GF6451@chaz.gmail.com> (raw)
In-Reply-To: <20150604103819.GE6451@chaz.gmail.com>
2015-06-04 11:38:19 +0100, Stephane Chazelas:
[...]
> I wonder how/when gmane adds those cross-post headers.
>
> (I'm posting this answer on zsh.devel, I don't know if yours was
> posted on users or workers).
[...]
Well, here gmane doesn't strip the "To/Cc" headers, so I could
know.
See also
http://thread.gmane.org/gmane.comp.shells.zsh.user/4275/focus=7744
posted 2 days short of 10 years ago already mentioning the
same issue.
--
Stephane
next prev parent reply other threads:[~2015-06-04 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 9:45 Yuri D'Elia
2015-06-04 10:38 ` Stephane Chazelas
2015-06-04 11:01 ` Stephane Chazelas [this message]
2015-06-04 16:09 ` Yuri D'Elia
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=20150604110158.GF6451@chaz.gmail.com \
--to=stephane.chazelas@gmail.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).