On Wed, Oct 13, 2010 at 2:28 AM, Allison Randal <[email protected]> wrote: > On 10/12/2010 04:45 PM, James E Keenan wrote: >> >> This is the first time I've heard of the two different tickets lists. >> What are their individual names (or other distinguishing >> characteristics)? Which one is 'reply-all' working with? >> >> Is this under our control? Or is it administered by OSUOSL? > > There is only one ticket *list*, <[email protected]>.
Sorry, was sending from my phone and was lazy. ;) > There is also an email address <[email protected]>, which is a dedicated > address for Trac's ticketing system. Messages sent there are added as a > comment on the relevant bug (Trac parses the email to extract the ticket > number). This was necessary to set up the "ticket comments from email" > feature that many people wanted duplicated from the old RT system. > > OSU OSL administers both the mailing list and the email address for Trac. > "Reply all" goes to both, but a simple "Reply" only goes to > <[email protected]> (that is, it goes into Trac, but not to the mailing > list). Some email clients also have a "Reply list" feature, which only goes > to the mailing list. > > Allison > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev > I'm using Gmail (the hosted domain version) On Tue, Oct 12, 2010 at 10:58 PM, Parrot <[email protected]> wrote: > #435: languages moved to examples need tests. Hitting reply all shows me only parrot-tickets. On Tue, Oct 12, 2010 at 11:01 PM, Parrot <[email protected]> wrote: > #443: C API brought into line with coding standards Reply all shows parrot-tickets & tickets. Looks like the Reply-to was not set in the first message, but is in the second. -- Will "Coke" Coleda _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
