From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Proposal: send gitlab notifications to this list
Date: Mon, 28 Nov 2016 10:47:31 +0100 [thread overview]
Message-ID: <583BFD33.7030705@codethink.co.uk> (raw)
Hi,
I think it would be positive to activate the mail notifications from
gitlab and send them to this list.
By activating them, you will be able to follow what is happening in our
repos through mail. Using filters in your e-mail client you can manage
the notification mails, so you "keep clean of notifications" this list
if you need to.
I believe the traffic will not be much for now so the traffic will be
affordable in a single list. We can move notifications to a new list
when the activity grows.
What do you think?
Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next reply other threads:[~2016-11-28 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 9:47 Agustin Benito Bethencourt [this message]
2016-11-28 12:11 ` [cip-dev] Proposal: send gitlab notifications to this list Wolfgang Mauerer
2016-11-28 12:36 ` KOBAYASHI Yoshitake
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=583BFD33.7030705@codethink.co.uk \
--to=agustin.benito@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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