Re: Bug tracker tool we need - Mailing list pgsql-hackers

From Christopher Browne
Subject Re: Bug tracker tool we need
Date
Msg-id CAFNqd5VPzk1b=1O23GHZUyjM+JoDWiv4dDsawBVNxiQikZc1Yg@mail.gmail.com
Whole thread Raw
In response to Re: Bug tracker tool we need  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Bug tracker tool we need
List pgsql-hackers
On Thu, Apr 19, 2012 at 10:49 AM, Magnus Hagander <magnus@hagander.net> wrote:
> On Thu, Apr 19, 2012 at 16:45, Greg Sabino Mullane <greg@turnstep.com> wrote:
>>
>>>> My github.com account currently has 4264 notifications in the inbox.
>>>> Almost all of those are spam, growing constantly. �Because of that, the
>>>> platform is currently fairly useless to me for actually communicating or
>>>> collaborating on code.
>>>
>>> That's about the same amount that I have.
>>
>> I have no spam at all, despite being a fairly early github adopter.
>> Wonder what the difference is?
>
> The vast majority of the spam I have originates in the postgresql git
> repository. You don't have any commits there...
>
> But I would've assumed it should hit equally hard on other
> repositories that's been around a long time.

I have plenty of commits on the Slony Git repo, which has had clones
at github for about as long as PostgreSQL has.

And I don't get any noticeable amounts of spam at github.  Not all
notifications are hugely interesting, but I don't see anything that's
not reasonably related to things I have commented on.

So I think there has to be some other effect in play.
--
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Bug tracker tool we need
Next
From: Nikhil Sontakke
Date:
Subject: Re: how to create a non-inherited CHECK constraint in CREATE TABLE