From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 1/1] travis: initial configuration
Date: Wed, 11 Jan 2017 16:49:58 +0100 [thread overview]
Message-ID: <20170111154957.GA10729@rei.lan> (raw)
In-Reply-To: <20170111125937.19842-1-petr.vorel@gmail.com>
Hi!
I did some tests with email notifications and figured out that anything
else than having the mailing list address hardcoded in the travis config
is pretty much useless since neither the commited nor the patch author
gets email unless they are registered in travis.
So I will commit the V1 patch that has the mailing list address in the
config to see if that is a workable solution. Hopefully that will not
spam the mailing list too much.
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2017-01-11 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 12:59 [LTP] [PATCH v2 1/1] travis: initial configuration Petr Vorel
2017-01-11 15:49 ` Cyril Hrubis [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=20170111154957.GA10729@rei.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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