It's not a surprise. If you read the notice I sent out, you would know it's a expected problem when you're new to this policy.
-1 on revert to old policy. --Sheng On Feb 7, 2013 6:45 AM, "Chip Childers" <chip.child...@sungard.com> wrote: > On Thu, Feb 07, 2013 at 01:04:07PM +0200, Alex Karasulu wrote: > > Ooops sent this to Brett directly. Thanks for the heads up Brett. > > > > And here's our problem! > > Can we please ask to have the change reverted? > > > > > On Thu, Feb 7, 2013 at 12:21 PM, Alex Karasulu <akaras...@apache.org> > wrote: > > > > > > > > > > > > > > On Thu, Feb 7, 2013 at 4:36 AM, Brett Porter <br...@apache.org> wrote: > > > > > >> > > >> On 07/02/2013, at 12:05 PM, Sheng Yang <sh...@yasker.org> wrote: > > >> > > >> > The previous setting won't respect CC after the CCed guy replied > mail. > > >> > I don't think that's useful. > > >> > > > >> > I truly believe it's developer's responsible to keep track of their > > >> > own topic, but I also think make it easier for developer to keep > track > > >> > is better. > > >> > > > >> > > >> This seems like an edge case to me... most of the time a developer > that > > >> contributes to a thread will remember to follow that subject (as I am > doing > > >> here). If that might be a problem, they have alternatives: > > >> - CC themselves on messages they send, so they remain on the CC list > > >> - set up filters to label threads that include their name > > >> > > >> Do these seem like better alternatives than altering the list > reply-to? > > >> > > >> > > > I agree with Brett here. Filters are a life saver by the way. > > > > > > Also with the javelin branch merged, some of the envisioned > > > component-ization activities might enable a better mailing list > > > organization. This is all good stuff to consider and possibly take > care of > > > at graduation time if it still seems necessary. WDYT? > > > > > > -- > > > Best Regards, > > > -- Alex > > > > > > > > > > > -- > > Best Regards, > > -- Alex >
