Re: Fighting commit storm madness (was: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1)
On Friday, October 10, 2014 00:22:42 Dimitri John Ledkov wrote:
> On 9 October 2014 20:57, Scott Kitterman <debian@kitterman.com> wrote:
> > On October 9, 2014 10:43:38 AM EDT, Barry Warsaw <barry@debian.org> wrote:
> >>On Oct 09, 2014, at 10:19 AM, Scott Kitterman wrote:
> >>>Upstream commits are off topic.
> >>
> >>Agreed. There's no reason why we need notifications of upstream
> >>commits,
> >>though I don't know if it's possible to filter them out.
> >>
> >>>I'm probably going to give up on hanging out on #debian-python once we
> >>
> >>get
> >>
> >>>more packages in git. The commits are way too much and don't add
> >>
> >>value.
> >>
> >>Have you seen #debian-openstack-commits? Maybe we should just create a
> >>#debian-python-commits channel and send the notifications, and only the
> >>notifications, there. That way, it doesn't clutter up the discussion
> >>channel,
> >>and people can choose to join the -commits or not.
> >>
> > If there's no way to avoid the upstream stuff, I guess that's what we'll
> > have to do. I would prefer not though. I sometimes find the existing
> > commits valuable.
> >
> > Scott K
>
> Given that notifications operate as git server hooks (I presume), one
> should have full facility to filterdiff the commit emails and discard
> notifications for commits that do not change anything under "debian/*"
> paths. Or don't have debian/ subdir to begin with.
Presumably "one" is the one who set up the git repos. I, for another one,
would really appreciate it if someone would take care of this.
Scott K
Reply to: