From: Andreas Schwab <schwab@linux-m68k.org>
To: Jan Stranik <jan@stranik.org>
Cc: ding@gnus.org
Subject: Re: Proper use of message-alternative-emails configuration variable
Date: Sat, 06 Jul 2013 09:05:21 +0200 [thread overview]
Message-ID: <m28v1kmamm.fsf@linux-m68k.org> (raw)
In-Reply-To: <8761wphr0n.fsf@jo.jans.selfip.org> (Jan Stranik's message of "Fri, 05 Jul 2013 13:10:16 -0400")
Jan Stranik <jan@stranik.org> writes:
> The effect is that when I reply to my non-primary address, I always get
> added to CC'ed on the mail and I receive my own reply as well.
Try adding it to message-dont-reply-to-names.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2013-07-06 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 17:10 Jan Stranik
2013-07-06 7:05 ` Andreas Schwab [this message]
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=m28v1kmamm.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=ding@gnus.org \
--cc=jan@stranik.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 NNTP newsgroup(s).