I don't think it's possible to use a custom prefix for issues, so I've
create a new dblinq-bugs group at Google Groups, which should now
receive issue emails.  Sign up at:

    http://groups.google.com/group/dblinq-bugs

 - Jon

On Thu, 2009-05-14 at 09:29 +0200, Giacomo Tesio wrote:

> I agree for a different group. 
> Alternativelly we should allow some tagging for email coming from
> issue tracker (a [ISSUE] prefix in the subject or the so).
> 
> 
> Giacomo
> 
> 
> 
> On Wed, May 13, 2009 at 8:49 PM, Jonathan Pryor <[email protected]>
> wrote:
> 
>         
>         On Wed, 2009-05-13 at 13:39 -0400, Adam Tauno Williams wrote:
>         > Possibly a dumb question; but can the Google Issues "app"
>         notify the
>         > mailing list when something is created/commented/etc...
>          This list is
>         > fairly low volume [and generally very interesting] so it
>         doesn't seem
>         > like the "extra" traffic would be a problem.
>         
>         Yes it can.  Alas, it can only be sent to one email address
>         (odd, that).
>         
>         So we could either send the issue emails to this list, or we
>         could
>         create a new Google group specifically for the issue emails
>         (and then
>         anyone could subscribe to that group if they want to receive
>         Issue
>         emails).
>         
>         I'm inclined to create a new group for issue emails, and will
>         do so
>         unless a majority of people responding by tomorrow would
>         rather use this
>         list.
>         
>          - Jon
>         
>         
>         
>         
> 
> 
> 
> > 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"DbLinq" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/dblinq?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to