public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
* [cip-dev] Proposal: send gitlab notifications to this list
@ 2016-11-28  9:47 Agustin Benito Bethencourt
  2016-11-28 12:11 ` Wolfgang Mauerer
  2016-11-28 12:36 ` KOBAYASHI Yoshitake
  0 siblings, 2 replies; 3+ messages in thread
From: Agustin Benito Bethencourt @ 2016-11-28  9:47 UTC (permalink / raw)
  To: cip-dev

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [cip-dev] Proposal: send gitlab notifications to this list
  2016-11-28  9:47 [cip-dev] Proposal: send gitlab notifications to this list Agustin Benito Bethencourt
@ 2016-11-28 12:11 ` Wolfgang Mauerer
  2016-11-28 12:36 ` KOBAYASHI Yoshitake
  1 sibling, 0 replies; 3+ messages in thread
From: Wolfgang Mauerer @ 2016-11-28 12:11 UTC (permalink / raw)
  To: cip-dev

Hi Agustin,

Am 28/11/2016 um 10:47 schrieb Agustin Benito Bethencourt:

> 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?
That's a good idea, albeit we could also think about doing development
completely kernel-style, with a review of patches on the mailing list
(the fact that a patch has been merged or a bug has been opened is IMHO
not as interesting as what should go into the repo).

Best regards, Wolfgang
> 
> Best Regards
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [cip-dev] Proposal: send gitlab notifications to this list
  2016-11-28  9:47 [cip-dev] Proposal: send gitlab notifications to this list Agustin Benito Bethencourt
  2016-11-28 12:11 ` Wolfgang Mauerer
@ 2016-11-28 12:36 ` KOBAYASHI Yoshitake
  1 sibling, 0 replies; 3+ messages in thread
From: KOBAYASHI Yoshitake @ 2016-11-28 12:36 UTC (permalink / raw)
  To: cip-dev

Hi Agustin,

> What do you think?

Thanks for the suggestion. I think it is a nice idea.

Best regards,
Yoshi

On 2016/11/28 18:47, Agustin Benito Bethencourt wrote:
> 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
>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-11-28 12:36 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-11-28  9:47 [cip-dev] Proposal: send gitlab notifications to this list Agustin Benito Bethencourt
2016-11-28 12:11 ` Wolfgang Mauerer
2016-11-28 12:36 ` KOBAYASHI Yoshitake

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox