From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Mailing list address
Date: Mon, 14 Sep 2015 07:58:34 -0300 [thread overview]
Message-ID: <55F6A85A.1050202@zacarias.com.ar> (raw)
In-Reply-To: <55F6A7E1.4090500@imgtec.com>
On 14/09/15 07:56, Vicente Olivert Riera wrote:
>> I haven't
>> seen a bounce but haven't seen it show up on the list yet.
>
> I do see your patch on the list, and also in Patchwork:
>
> http://patchwork.ozlabs.org/patch/517337/
Hi.
That's called duplicate supression, many mail servers do that.
Since git-send-email is CCing you you've already got the message, hence
when the mailing list email arrives it's supressed because it's a duplicate.
Regards.
next prev parent reply other threads:[~2015-09-14 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 10:35 [Buildroot] Mailing list address Chris Packham
2015-09-14 10:56 ` Vicente Olivert Riera
2015-09-14 10:58 ` Gustavo Zacarias [this message]
2015-09-14 22:40 ` Chris Packham
2015-09-14 12:41 ` Peter Korsgaard
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=55F6A85A.1050202@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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